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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds real value by clarifying that the output is advisory (warnings) and that nothing is repaired, but says nothing about how the issues are produced or returned.

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?

A single front-loaded sentence with no filler. It is efficient, though the terseness comes partly at the cost of missing scope detail.

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, the description usefully signals that the return is a set of advisory issues and warnings. However, for a tool keyed on a promotion_id it never explains that identifier, and no output shape or severity semantics are given.

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% for the single required parameter promotion_id, and the description never mentions it or its meaning. The description therefore does nothing to compensate for the undocumented parameter, unlike the baseline-3 case where the schema already carries the semantics.

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 states a verb ("Read") and a resource ("saved advisory readiness issues and warnings"), but never mentions promotions, so the tie to the tool name validate_promotion is left implicit. It also doesn't distinguish itself from near-neighbours like get_promotion_report or preview_promotion, which an agent could easily confuse with it.

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 call this versus the sibling tools that also surface promotion state (get_promotion_report, preview_promotion, get_promotion). The agent must infer the selection criteria entirely from the tool name.

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