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: no read-only nature, no rate limits, no scope of the searched corpus, no result shape. A one-line restatement of the identifier leaves the agent with zero behavioral information.

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 this is under-specification rather than earned conciseness. The single sentence duplicates the name and title, so no sentence adds information an agent could not already read from the tool identifier.

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 tool with no annotations, no output schema, and no return-format documentation, the description should at minimum explain what corpus is searched and what the agent gets back. It omits both, leaving the agent unable to distinguish this from the shared:: or other-framework variants beyond the prefix in the 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?

Schema description coverage is 100% — the single 'query' parameter is documented as 'Search terms for bundled SDK references,' including a maxLength of 500. Per the baseline rule for high coverage, a 3 is appropriate; the description adds no syntax, format, or matching-semantics detail 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 essentially a restatement of the tool name with a namespace prefix: 'MediaSFU Vue :: api.reference.search (reference-search).' It conveys no verb or resource explanation beyond what the identifier already encodes, and offers no differentiator against the dozens of parallel <framework>::api.reference.search siblings.

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 mention of when this is preferable to the other framework-scoped reference search tools, and no prerequisites such as whether a bundled SDK must be installed first. Nothing is stated or even implied beyond the name.

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