Search YAGOO Directory

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

Annotations already indicate a safe read-only, idempotent operation. The description adds meaningful behavioral context: it indexes 56 agents across 10 categories, returns ranked results, and is a directory guide. This goes beyond annotations without contradicting them.

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 well-structured with a clear purpose, bulleted use cases, and an Args/Returns section. It is appropriately concise—every sentence earns its place—and front-loaded with the core purpose.

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?

With no output schema, the description compensates by specifying the return format: 'Ranked list of matching agents with relevance scores and recommendations.' It also provides context about the directory size and categories, making it complete for a search tool.

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%, providing full parameter descriptions. The description adds value by giving natural language examples for query (e.g., 'scrape websites'), clarifying the pricing filter, and noting the default limit of 5. This enriches the schema without redundancy.

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 'Search the YAGOO agent directory to find the right AI agent for a task,' using a specific verb and resource. It distinguishes itself from siblings like yagoo_get_agent and yagoo_compare by focusing on search and discovery.

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 explicitly lists when to use the tool: recommend an agent, find alternatives, and discover agents by category. It does not explicitly name alternatives or state when not to use it, but the usage contexts are clear enough to guide an agent.

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