search_context

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

No annotations provided, so description must fully describe behavior. It only says 'read-only search with context' but doesn't explain how context is returned (e.g., line numbers, number of surrounding lines, format). Fails to disclose pagination, sorting, or any side effects.

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, no redundancy. Could benefit from front-loading the primary use case (search with context) but is appropriately brief.

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 6 parameters, no output schema, and no annotations, the description is too sparse. Does not explain return value structure, which would help agents parse results for further actions.

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 only 17% (only 'vault' described). Description adds no parameter-level detail. Agents must infer that 'limit' controls result count and 'format' controls output style from defaults/enums alone.

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 the tool is a read-only search that provides surrounding line context. Distinguishes from siblings like 'search' (which likely returns just file paths without context). Could be more specific about what 'context' entails.

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 guidance on when to use this tool versus other search tools (e.g., 'search', 'deadends', 'links'). No mention of prerequisites or exclusions.

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