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

No annotations are provided, so the description carries the full burden of behavioral disclosure, and it discloses nothing: no read-only/analysis framing, no scope limits, no indication of what the search operates over or how results are bounded.

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?

It is short, but that brevity comes from under-specification rather than economy. The one sentence present is pure boilerplate identifier text and earns no 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?

With no annotations, no output schema, and a dense family of near-identical sibling tools, the description must at minimum establish scope (Angular-specific bundled SDK references) and result behavior. It establishes neither, leaving the agent unable to distinguish this tool from its many counterparts.

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 the single required 'query' parameter is already documented as 'Search terms for bundled SDK references.' The description adds no meaning beyond the schema, so the baseline of 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?

The description is a namespaced restatement of the tool name ('MediaSFU Angular :: api.reference.search (reference-search)') with no verb or explanation of what searching actually returns or covers. An agent learns nothing beyond the identifier it already has.

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 when-to-use guidance is given. The SDK-reference search sits alongside dozens of siblings (fix.suggest, feature.map, sdk.recommend, runtime.diagnose) and framework variants (android/android/flutter/kotlin...), and the description does not say when to reach for reference search versus those alternatives.

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