find_tools

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

No annotations are provided, so the description must disclose behavior. It states it returns ranked matches with descriptions, which gives the return format. However, it does not mention whether the operation is read-only, any authentication requirements, or potential errors. For a search tool, this is adequate but not highly transparent.

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?

The description is concise (two sentences) and front-loaded with the core action and examples. 'Start here' is a useful directive. No unnecessary words or repetition.

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 the tool's simplicity (3 params, no output schema), the description covers what it does, gives concrete examples, and specifies the return type (ranked matches with descriptions). The schema handles parameter details, so the description is complete for an agent to correctly invoke it.

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 coverage is 100% with clear descriptions for each parameter (query, limit, category). The tool description adds no extra parameter information beyond the schema, but the schema already provides sufficient meaning. Baseline of 3 applies because the description does not need to compensate.

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 the tool's purpose: to search the yala toolkit's 500+ CLI utilities by task. It uses a specific verb ('search') and resource ('yala toolkit's 500+ standalone CLI utilities'), and includes examples. This distinguishes it from siblings like tool_info (specific tool details), run_tool (execution), and list_categories (category listing).

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 phrase 'Start here' clearly positions this as the entry point for finding tools, implying it should be used before other tools when you need to locate a utility. However, it does not explicitly state when not to use it or mention alternative tools, though the context provides enough guidance for an agent.

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