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: not the search scope, not the result format, not whether results are ranked or paginated, not whether the index is local or remote. The alias list is metadata, not behavioral context.

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 the brevity is under-specification rather than conciseness. The one fragment is a namespaced identifier plus aliases, so no sentence actually earns its place by telling an agent what the tool does.

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?

For a search tool with one required parameter, no annotations, and no output schema, the description should at minimum say what is being searched and roughly what comes back. Neither is covered, leaving the agent to infer everything from the tool name.

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?

The single parameter 'query' already has a full schema description ('Search terms for bundled SDK references.'), giving 100% schema coverage. The description adds no syntax, format, or example guidance beyond that, so the baseline 3 for high-coverage schemas 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 essentially the tool name restated with a namespace prefix and an alias list ('MediaSFU Unity :: api.reference.search (reference-search). aliases: unity, unity-sdk, csharp-unity'). It never states in plain language that it searches bundled SDK references, what corpus it covers, or how it differs from siblings like unity::sdk.recommend or unity::feature.map. This is close to a tautology.

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 when-to-use guidance, no exclusions, and no named alternative. The only weak signal is the token 'search' in the name, which implies a lookup use case but gives no condition for choosing it over the SDK-recommendation or feature-mapping siblings.

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