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 delivers none. It says nothing about the return format, whether results are ranked or paginated, or what 'bundled SDK references' actually contains.

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 brevity here reflects under-specification rather than efficient conciseness. The single sentence is essentially a namespace-qualified restatement with zero actionable content.

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 output schema and no annotations, the description should explain what a search returns and how results should be used, but it does not. For a search tool operating over SDK references, this leaves the agent without enough context to use it confidently.

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 'query' parameter is documented in the schema as 'Search terms for bundled SDK references.' Per the high-coverage baseline, 3 is appropriate; the description adds no meaning beyond the schema.

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 tautology: 'MediaSFU React Native :: api.reference.search (reference-search)' merely restates the tool name and adds nothing about what it does. The name implies searching bundled SDK references, but the description text itself provides no verb+resource explanation or sibling differentiation.

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?

There is no guidance at all about when to use this tool versus alternatives. It does not mention the many sibling api.reference.search variants across other platforms, nor when an agent should prefer it over fix.suggest or feature.map.

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