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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds useful context by stating it 'report[s] missing or ambiguous replacements', giving insight into the tool's output and success criteria. It does not detail side effects, but annotations cover the safety profile.

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 description is a single concise sentence that front-loads the main action and outcome. Every word contributes meaning, with no filler or redundancy.

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 output schema and five required parameters, the description is underspecified. It does not explain the return format, how 'ambiguous' is determined, whether exact matches are also reported, or any prerequisites. The tool is complex, so the description should provide more detail to be fully actionable.

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%, so the description must compensate. It mentions 'packages' and 'distribution release' but does not clarify the distinct roles of source_distro, source_release, target_distro, and target_release, nor their expected formats. The parameter names are somewhat self-explanatory, but the description adds little beyond the schema's property names.

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 uses a specific verb ('Map') and resource ('packages from one distribution release to another') with a clear outcome ('report missing or ambiguous replacements'). It clearly distinguishes from sibling tools like compare_distro_releases and compare_package_versions, which focus on raw comparisons rather than migration mapping.

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 description implies a clear use case: planning package migrations between distribution releases. However, it does not explicitly mention when not to use it or point to alternative tools for similar tasks, so it stops short of full exclusions guidance.

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