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

No annotations are provided, so the description carries the full disclosure burden, and it discloses nothing: no side effects, no whether mapping is a pure lookup or triggers configuration, no rate limits, no return shape. The only content is a restated identifier.

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 comes from under-specification rather than efficiency. There is no front-loaded statement of purpose or scope to anchor the reader.

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 single parameter, the description should explain inputs and expected response. It provides none of that, leaving an agent unable to call the tool confidently.

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 item description is just "Required feature." The description does not explain what a 'feature' string looks like, accepted values, or that the array is capped at 32 unique items, so it fails to compensate for the coverage gap.

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?

"feature.map (mapper)" restates the tool name and adds the word "mapper," but never says what is being mapped to what (e.g., requested features to MediaSFU SDK APIs) or what the output is. An agent cannot distinguish it from siblings like sdk.recommend or integration.plan beyond guessing.

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, when not to, or which sibling (sdk.recommend, integration.plan, api.reference.search) covers adjacent needs. Across ~100 sibling tools sharing the same pattern, the description offers no routing signal.

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