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

Annotations already establish that this is read-only and closed-world. Beyond that, the description adds the full lifecycle-state vocabulary and the important caveat that SETTLED occurs only on the provider's own confirmation, which is useful behavioral context; it does not address polling, freshness, or error 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?

The description is compact and front-loads the state list followed by the settlement caveat. The meta reference to "Spec v1.0 name for payment_run_status" is somewhat confusing and does not clearly earn its place.

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 simple read-only status tool with fully described parameters and no output schema, the description gives enough of the return semantics via the lifecycle states and reason. The main gap is that it does not clarify how this relates to the payment_run_status sibling in practical selection terms.

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%, so the schema already documents run_id and access_key. The description does not add meaning about parameter usage or constraints beyond what the schema provides, making the baseline 3 appropriate.

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 makes clear that this returns each payment's lifecycle state and the reason, with a concrete state list. The opening phrase, "Spec v1.0 name for payment_run_status," introduces sibling/alias ambiguity and lacks an explicit retrieval verb, so it is strong but not fully crisp.

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 guidance on when to use this tool, when not to use it, or when to prefer it over payment_run_status or related status tools. The title implies tracking, but the description does not state the triggering context or alternatives.

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