find_tools

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

Discloses the behavioral effect: matching tools 'become callable immediately after.' With no annotations provided, the description carries full burden and transparently explains the tool's side effect of activating hidden tools.

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?

Description is well-structured with a clear front-loaded purpose statement and helpful examples, but is slightly wordy; however, every sentence adds 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?

Given only one parameter, no output schema, and no annotations, the description thoroughly explains the tool's role in the system, how to use it, and its outcome, making it fully complete for an AI agent.

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 single parameter 'query' already has a good schema description, but the tool description adds rich context (examples, categories) beyond the schema, as schema coverage is 100%.

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?

Description explicitly states the tool discovers more WhatsApp tools not currently active, with a specific verb 'discover' and resource 'WhatsApp tools'. It distinguishes its role from sibling tools by positioning it as a first-resort tool when visible tools don't cover the need.

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?

Provides explicit when-to-use guidance: 'Call this FIRST whenever you need an action or data that the visible tools do not cover.' Lists example categories and instructs to pass a short description, leaving no ambiguity about invocation context.

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