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

No annotations are provided, so the description must carry the entire behavioral burden, and it discloses nothing: not whether this is a read-only lookup, what it returns, whether it depends on prior scaffold/env steps, or any rate or auth constraint. Nothing beyond the tool's own name is communicated.

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 shortness here reflects under-specification rather than efficiency; the one clause present is redundant with the name. There is no front-loaded statement of what the tool actually 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?

With no annotations, no output schema, an undocumented parameter, and a dense sibling namespace, this description is entirely inadequate for an agent to call the tool correctly. Nothing reusable would be lost if it were deleted.

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 requestedFeatures has 0% schema description coverage (only the item-level string says "Required feature."), and the description adds no explanation of accepted feature identifiers, format, or expected cardinality. Nothing compensates for the schema gap.

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?

"MediaSFU Vue :: feature.map (mapper)" is a tautology that restates the name and title; the parenthetical "mapper" is the only hint of purpose. It names no verb or resource and gives no sense of what feature mapping produces, so an agent cannot distinguish it from siblings like vue::sdk.recommend or vue::integration.plan.

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 whatsoever on when to invoke this tool, what prerequisites exist, or which sibling to prefer. The large parallel family of tools per framework makes routing without such guidance pure guesswork.

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