Undocumented tool-name suffix causes policy hooks to silently no-op

While building custom policies extending AbstractPolicy for the Week 5 bounty, I discovered that relevant_tools must list the exact method name (e.g. "transfer_hbar_tool"), not the tool's base name ("transfer_hbar").

This mismatch causes the hook guard (if method not in relevant_tools: return) to silently skip the policy — transactions pass through unguarded with no error or warning.

Suggestion: document the exact method-name strings in the AbstractPolicy example, or add a debug log when a hook is registered but never matches any tool. This would save builders significant debugging time.

Start with the AbstractPolicy example and the relevant_tools hook guard described in the issue. Document that relevant_tools must use exact method names such as "transfer_hbar_tool", not base names such as "transfer_hbar"; done means builders can identify the required strings without relying on silent behavior.

Written by the indexing model from the issue text.