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

No annotations are supplied, so the description carries the full burden of behavioral disclosure, and it says nothing about whether the operation is read-only, what it returns, or whether the mapping is deterministic. An agent has no way to know if calling it mutates anything or what shape the result takes.

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 economy: one fragment that repeats the tool identifier. No front-loaded purpose statement earns its place because none exists.

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 an undocumented parameter, the description leaves an agent unable to determine inputs, outputs, or side effects. For a mapping/lookup tool in a large family of similarly named siblings, this is inadequate.

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% for the sole parameter, and the description adds no information about requestedFeatures beyond its name. The schema's maxItems/uniqueItems constraints provide some structure, but the description does nothing to explain what a 'mapped' feature looks like or how input features relate to output.

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 merely restates the tool name with a platform prefix: 'MediaSFU Kotlin :: feature.map (mapper)'. The bare word 'mapper' hints at a lookup/translation operation but never states what is being mapped to what, so it does not distinguish this tool from the sibling feature.map tools on android, flutter, swift, unity, etc.

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 statement of when to use this tool, what inputs it expects, or how it differs from alternatives such as sdk.recommend or integration.plan. The only implicit cue is the 'kotlin::' prefix, which an agent must infer from the name rather than the description.

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