find_definitions

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

No annotations provided; description must disclose behavior. It states returns include 'definition details, lines, and exact code snippet', implying read-only. However, no details on scope, prerequisites (e.g., indexing), error conditions, or limitations. Adequate but not thorough.

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?

Single, concise sentence with no redundancy. Every word is necessary to convey the tool's action and result.

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 a simple tool with one parameter and no output schema, the description adequately covers what it does and returns. Could mention error cases or indexing requirements, but overall sufficient for the complexity.

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% for one parameter. The description adds minimal value beyond the schema's 'description' field—both mention symbol types and examples. Baseline 3 as schema does the heavy lifting.

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 action ('Returns') and the specific resource ('definition details, lines, and exact code snippet') for a given symbol. It explicitly lists symbol types (function, class, method) and distinguishes from siblings like find_references.

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?

No explicit when-to-use or when-not-to-use guidance. The intended use is implied by the description (find definition of a symbol). Sibling tools like find_references provide implicit contrast, but no exclusions or alternatives are mentioned.

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