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/write nature, no side effects, no auth or environment requirements, no rate or size limits. 'mapper' conveys no behavioral trait.

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 comes from under-specification rather than efficient front-loading. The one line spends its space on a namespace prefix and a redundant parenthetical instead of information an agent can act on.

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 0% parameter coverage, this tool needs the description to explain the mapping operation and its feature inputs. It supplies none of that, leaving an agent unable to invoke it correctly.

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 0% and the single parameter 'requestedFeatures' is documented only by the terse item text 'Required feature.' The description adds nothing about the accepted feature vocabulary, maxItems 32, or uniqueItems constraints.

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 'MediaSFU Android :: feature.map (mapper)' only restates the tool name and its parenthetical alias 'mapper'. It never says what is mapped, from what to what, or what output the mapping produces, so it is effectively a tautology rather than a statement of purpose.

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 on when to use feature.map versus any of its many siblings (integration.plan, app.scaffold, ui.mode.recommend, etc.), nor any precondition or exclusion. An agent has no basis for choosing this tool over its neighbors.

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