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

No annotations are provided, so the description carries the full burden, and it discloses nothing: no read/write nature, no side effects, no permission needs, no output shape. For a tool with zero annotation coverage this is a complete behavioral void.

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 brevity here reflects under-specification rather than conciseness. The single fragment conveys no information an agent could not already read from the tool name.

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 large family of near-identically named siblings, the description should at minimum explain the mapping behavior and its outputs. It provides none of that, leaving the agent unable to distinguish or correctly invoke this tool.

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 description adds nothing about 'requestedFeatures'. The only hint in the entire definition is the schema's item description 'Required feature.', which does not explain format, allowed values, or how the list is interpreted.

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 'mediasfu-shared :: feature.map (mapper).' It merely restates the tool name and namespace, plus the parenthetical 'mapper' which repeats the name again. There is no verb, no resource explanation, and no indication of what mapping features actually means or produces.

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?

No guidance of any kind. It does not say when to call this versus the ~13 sibling tools per platform (api.reference.search, app.scaffold, integration.plan, sdk.recommend, etc.), nor what input condition should trigger it.

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