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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: no side effects, no whether it reads or writes, no output shape, no prerequisites. Aliases are pure identity metadata, not behavior.

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 a single terse line with no wasted sentences, so structure is fine, but the brevity is under-specification rather than effective concision. The identity prefix is front-loaded but the aliases consume space without informing tool use.

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 mapping tool with no output schema and no annotations, the description is entirely inadequate — an agent cannot tell what it returns, what valid feature strings look like, or how the result should be consumed. Nothing an agent needs to invoke it correctly is present.

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?

With one parameter and 0% schema description coverage, the description had to compensate and does not mention requestedFeatures at all. The only hint comes from the schema's own item text ('Required feature.'), which is ambiguous since the array itself is optional.

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 only restates the tool name ('feature.map (mapper)') and namespace, adding no verb+resource explanation of what mapping a feature actually means. It does disambiguate the platform (Unity/MediaSFU), but that is naming metadata rather than purpose. This is effectively a tautology of the name.

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 guidance on when to use this tool, when not to, or how it relates to siblings like unity::integration.plan or unity::api.reference.search, which also deal with feature/integration work. The agent must guess from the name alone.

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