search_symbols

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

Discloses FTS5 prefix syntax and return type, but lacks details on case sensitivity, partial matching, or error behavior. No annotations exist, so more depth would be beneficial.

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?

Three sentences, each serving a purpose: purpose, usage directive, and additional detail. No unnecessary words, well-structured.

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 existence of an output schema and simple tool nature, description covers return type and integration with other tools. Leaves out some edge cases but is generally sufficient.

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 description adds meaning for the undocumented 'query' parameter by explaining full-text search and prefix syntax. For 'limit', schema already provides description, so net positive.

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?

Description clearly states 'Search for symbols by name using full-text search', which is specific and distinguishes it from sibling tools focusing on references or calls.

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?

Explicitly says 'ALWAYS start here when you need to find a symbol', providing strong usage guidance. Could mention when not to use it, but the directive is clear.

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