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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered. The description does add real value by disclosing that reorganization and refund states are surfaced, which an agent would not expect from a generic 'status' tool, plus that a recommended next action is returned. It does not say whether results are eventually consistent or how often to re-query.

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?

One sentence, front-loaded with the resource and its states, with the payload summary ('next action to take') at the end. The nominal list of lifecycle words is slightly dense but every term carries information; no filler sentences.

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?

A read-only, single-parameter tool with an output schema, so the description need not explain return values. Covering lifecycle states plus the next-action field is close to sufficient; only guidance on when in the payment flow to call it, and expected polling behavior, is missing.

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 100%: the single parameter payment_intent_id is documented with its pattern and its origin ('from the quote'). The description mentions the parameter not at all, so it adds nothing beyond the schema; baseline 3 applies.

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?

States a specific resource (a payment) and enumerates the exact lifecycle facets it reports: detection, confirmations, settlement, failure, reorganization, refund. An agent can tell this is the read-side status lookup rather than a mutation like dmd_complete_purchase. It stops short of naming a sibling it differs from, so a 5 is not warranted.

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 explicit when-to-use or when-not-to-use statement, no mention of alternatives, and no prerequisite (e.g. 'call after dmd_create_did_payment_quote / purchase'). The 'next action to take' phrase implies a follow-up workflow but never says when to poll or how the result should drive the next call.

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