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

Annotations already declare readOnly, non-destructive, closed-world behavior, so safety is covered. The description adds genuinely useful context beyond that: matching is substring (not fuzzy or semantic), and the searched corpus includes guide bindings, not just tool records. It does not cover pagination or result ordering, but it clears the lower bar set by the annotations.

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?

A single front-loaded sentence with no padding, and the search scope comes first. The parenthetical 'EP-219: bound step, construct, tension' is somewhat opaque internal jargon that may not help an agent, keeping it from a 5.

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?

An output schema exists, so return values need not be described, and the parameters are fully covered by the schema. The missing piece is routing guidance among the six siblings, which matters for a search tool competing with list_tools and get_concept.

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% and both parameters are documented in the schema (including limit default and max). The description adds no syntax or format detail about 'q' or 'limit', which is acceptable given the schema does the work; baseline 3.

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?

States a specific verb+resource: substring search over the SE tools catalog and its guide bindings. The scope ('across the catalog and its guide bindings') is concrete and distinct from a plain listing. It does not explicitly contrast itself with the closest sibling, list_tools, so it stops short of a 5.

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 says what is searched but never states when to use this instead of list_tools or get_concept, nor any prerequisites or exclusions. The reader must infer that a substring query implies this tool.

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