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

No annotations are provided, so the description carries the full burden of behavioral disclosure, and it says nothing: no mutation/read character, no auth requirements, no limits beyond what the schema shows, no output shape. '(mapper)' conveys no behavioral trait an agent could act on.

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?

The single line is short but under-specified rather than concise — it front-loads a namespace prefix and a parenthetical that duplicates the tool name, spending its only words on restatement instead of useful content.

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, no parameter documentation, and a name-restating description, an agent has nothing to decide how or whether to call this tool. For a mapping operation that presumably returns a mapping result, this is wholly 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% and the description never mentions 'requestedFeatures'. The schema does convey the array shape, a 32-item cap, and uniqueness, so some structure is visible, but the description adds no meaning about what the feature strings are or how they are matched.

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 essentially a restatement of the tool name: 'MediaSFU ReactJS :: feature.map (mapper).' Calling it a 'mapper' adds no verb or resource detail beyond the name, and it never explains what 'mapping features' actually accomplishes. It only situates the tool on the ReactJS platform.

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 indication of when to use this tool versus the many siblings (shared::feature.map, other platform feature.map variants, integration.plan, app.scaffold, etc.). The agent is left to infer that this maps requested features to something, 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.