List all AdvocateHub MCP tools

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds useful context: 'No tenant credentials required' and filtering capabilities. It doesn't contradict annotations and provides extra behavioral insight beyond the safety flags.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the main purpose, and packed with actionable details. The examples are relevant without unnecessary verbosity; every sentence contributes value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list tool with no output schema, the description covers return content, filtering options, and credential requirements. It's self-contained and complete; no missing aspects that an agent would need to know.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already describes both parameters fully (100% coverage). The description adds value with example keywords ('member', 'search', 'reward', 'challenge') and explains the credential scope enum more concretely, going beyond the schema definitions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Returns the complete catalog of AdvocateHub MCP tools with names and descriptions' with a specific verb and resource. It distinguishes itself from tool_search by noting it shows every tool when tool_search only shows a subset.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Use this to discover, search, find, or list every available tool when tool_search only shows a subset', giving a clear use case. It also provides filtering guidance with examples and the no-credentials requirement, which helps the agent decide when to invoke it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.