ble_spec_search

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

No annotations are provided, so the description carries the burden. It discloses that the tool returns matching snippets with line numbers and context, but does not mention any destructive behavior, rate limits, or authentication needs. For a search tool, the behavior is adequately described but not thoroughly.

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 a single sentence that efficiently conveys the tool's function. It is front-loaded and contains no unnecessary words, though a slightly more structured format could improve scanability.

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?

The tool has no output schema, so the description explains the return format (snippets with line numbers and context). However, it omits details about the 'spec_id' parameter's semantics and does not provide examples or pagination behavior. Adequate but incomplete.

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?

Input schema coverage is 67%, with 'k' and 'query' having descriptions; 'spec_id' lacks description. The description adds no extra meaning beyond the schema; it only contextualizes that the search is 'over a spec's content', which hints at spec_id's role. Baseline of 3 is appropriate.

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 performs full-text search over a spec's content and returns snippets with line numbers and context. It uses specific verbs and resources, distinguishing it from siblings like ble_spec_get or ble_spec_read.

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 implies the tool is for searching spec content but lacks explicit guidance on when to use it versus alternatives, or any context on prerequisites or limitations. No when-not or sibling comparisons are provided.

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