cint_search_docs

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

No annotations are provided, so the description carries the full burden. It usefully discloses the default output mode ('compact output by default'), which hints at the verbose flag's tradeoff, but says nothing about result ranking, snippet format, or pagination behavior. For an inherently read-only search this is a moderate rather than severe gap.

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?

Two tight sentences with zero waste; the corpus scope is front-loaded and the output-mode note trails it. Every clause earns its place.

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?

There is no output schema, so the description should ideally characterize the returned results beyond 'compact output'. It covers corpus scope and default mode adequately, but with no annotations and no output schema the agent still has gaps around result shape and ranking.

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 description coverage is 100%, so all four parameters (query, scope, limit, verbose) are already documented in the schema. The description adds only the 'compact output by default' detail tied to verbose, so the schema does the heavy lifting — baseline 3 applies.

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?

Names a specific verb (Search) and enumerates the exact corpora it covers (SPEC-00P to SPEC-09P, GLOSSARY, ERRATA, curriculum CU-000 to CU-401). An agent understands what it searches, but the description never contrasts itself with overlapping siblings like cint_lookup_diagnostic, cint_list_curriculum, or cint_get_doc.

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 statement of when to use this tool versus the alternatives, despite clear overlap with cint_lookup_diagnostic (diagnostics) and cint_list_curriculum (curriculum). 'Compact output by default' is a behavioral note, not usage guidance.

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