search_legends

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

With no annotations, the description fully explains the tool's behavior: it searches across multiple fields and provides examples of query matches. It does not disclose potential limits like pagination or empty results, but for a simple search, this is adequate.

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: a short sentence defining the tool, followed by a list of example queries and a usage suggestion. No unnecessary words, front-loaded with 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?

Given the simple one-parameter tool, the description covers the key aspects: what it does, how to use it, and examples. It does not explain output format or error handling, but these are secondary 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?

The single 'query' parameter is described in the schema as matching name, description, tags, and expertise. The description adds value by providing concrete examples of queries and expected results, enhancing understanding beyond the schema.

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 states 'Search for legends by name, description, expertise, or tags,' providing a specific verb and resource. The examples further clarify the purpose, and it implicitly distinguishes from sibling tools like 'list_legends' which is for listing all legends.

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 says 'Use this for query-based discovery when you're not sure which legend to summon,' giving clear context. However, it does not explicitly mention when not to use or provide alternative tools for specific scenarios.

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