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 permissions, no rate limits, no indication whether output is a mapping table, a plan, or a code patch.

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?

Short, but brevity here reflects under-specification rather than economy — there is no directive sentence to front-load and the entire text is namespace plus aliases.

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 tool with no output schema, no annotations, and an undocumented parameter, the description supplies none of the missing information an agent would need to call it correctly.

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?

One parameter (requestedFeatures) at 0% schema description coverage, and the description never mentions it or the 80-char/32-item/unique constraints. The parameter name is semi-self-describing, which keeps this above a 1, but the description adds nothing.

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)" is a tautology that restates the tool name without saying what mapping actually produces. The only real content is the platform namespace and alias list, which identifies where it lives but not what it does.

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?

The alias list (apple, ios, ipados, macos, swift, swiftui, uikit) implicitly routes the agent to this platform variant over android/kotlin siblings, but there is no statement of when this tool should be used versus the many same-namespace siblings such as integration.plan or sdk.recommend.

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