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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing. It does not say the search is read-only, what corpus is searched, whether results are paginated, or what form results take; the identity string adds no behavioral signal at all.

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 emptiness rather than economy: the single line merely echoes the identifier from the name and title. There is no front-loaded statement of purpose, so no sentence 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?

With no annotations, no output schema, and only a name-echo for a description, an agent has almost nothing to decide when to call this versus the many sibling tools or what to expect back. For a search tool, the corpus, result shape, and scope are all unstated.

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% for the single 'query' parameter, which already documents it as 'Search terms for bundled SDK references.' The description adds nothing beyond the schema, so the 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 is essentially a tautological restatement of the tool name: 'api.reference.search (reference-search)'. It mentions the MediaSFU React Native Expo platform, which gives some scoping context, but never states in plain terms what the tool does (search bundled SDK references) or how it differs from the ~90 sibling search/scaffold/diagnose tools.

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, when-not-to-use, or alternative is given. At best the platform prefix implies this is the React Native Expo variant versus the react-native, reactjs, swift, etc. counterparts, but that routing information is left entirely to inference from the tool name rather than stated.

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