search_symbols

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

No annotations are provided, and the description does not disclose behavioral traits beyond the obvious read operation. It does not mention pagination behavior, rate limits, or what happens with empty results, leaving the agent to infer from parameter names alone.

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 sentence, front-loaded with the operation, minimal word count, zero fluff. Every word is functional.

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 8 parameters, no output schema, and no annotations, the description is too sparse. It lacks details on query syntax, limit/offset behavior, return format, and error conditions, making it insufficient for reliable agent invocation.

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?

With only 25% schema coverage, the description should add parameter context, but it only mentions 'name/signature' for query and 'optional language and node type filters'. It does not explain the format of 'query' (e.g., regex or substring), what 'signature' means, or how 'ignoreGlobs' filters work.

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 searches symbols by name/signature with optional filters across workspaces. It uses a specific verb and resource, but does not explicitly differentiate from siblings like 'get_references' or 'get_file_symbols', which might also relate to symbols.

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 guidance on when to use this tool versus alternatives. It mentions optional filters but does not indicate prerequisites, when not to use, or suggest alternatives among sibling tools.

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