toolfunnel_list_tools

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

With no annotations, the description carries full burden. It discloses the return format (list of {name, summary, category}) and that it's 'briefs only'. No destructive or side effects are implied, and the description is honest about what it provides.

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 concise sentences with no wasted words. The main action is front-loaded, and every sentence adds essential information without redundancy.

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 listing tool with optional filters, the description covers everything: what it returns, how to filter, and links to the next step. No output schema is needed because the return format is specified.

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?

Schema description coverage is 100%, so baseline is 3. The description adds value by explaining the purpose of filtering ('matched against tool name/summary') and the category restriction, but the schema already provides similar descriptions. However, the description contextualizes the parameters in the overall workflow.

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 it lists available tools with briefs, optionally filtered by text and/or category. It explicitly distinguishes from sibling tools by directing to toolfunnel_tool_instructions for specific tool details.

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?

The description provides a clear workflow: list tools, optionally filter, then use toolfunnel_tool_instructions for a specific tool. It explicitly mentions filtering options and tells when not to use this tool (for detailed instructions, use sibling).

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