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

Annotations are absent, so the description carries the full burden of behavioral disclosure, and it conveys nothing: no indication of whether the tool is read-only, whether it calls a backend, what it returns, or how it handles unmapped features. For a tool with zero annotation coverage this is a complete gap.

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 that brevity reflects under-specification rather than economy; the single line substitutes a tautology for the content an agent needs. Nothing is front-loaded because there is nothing substantive to front-load.

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 one-parameter tool with no annotations and no output schema, the description should explain the feature-mapping contract. Instead it says nothing about inputs, behavior, or results, leaving the definition unusable for correct invocation.

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 no meaning for 'requestedFeatures' beyond the schema's bare 'Required feature.' placeholder. The agent gets neither the expected string format, naming conventions, nor what happens with unknown or duplicate feature names (although maxItems and uniqueItems constrain shape).

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 Flutter :: feature.map (mapper)' merely restates the tool name and namespace, adding the platform label that the 'flutter::' prefix already supplies. It never states what is mapped to what or for which inputs, so an agent cannot tell whether it maps requested features to SDK capabilities, config flags, or something else.

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 when-to-use, when-not, or alternative selection guidance is present, despite many closely related siblings (integration.plan, sdk.recommend, api.reference.search). The agent is left to infer that 'feature mapping' is a planning-time step with no exclusions or prerequisites stated.

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