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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the readonly nature is covered. The description adds that only COMPLETED payments with matching fields can support reconciliation, which is useful but beyond that it doesn't reveal return format or edge cases. It doesn't contradict annotations.

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 brief and front-loads the key action (read one owned payment UUID). The second sentence adds context on reconciliation use. No fluff, but could be slightly more structured.

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?

The output schema exists, so return values are handled. For a simple single-parameter read with helpful annotations, the description covers the core. The reconciliation context is useful, but does not mention error scenarios or what happens for non-completed payments, which could be important for reconciliation.

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?

The schema already covers 100% of the parameter, including a detailed description 'Owned resource UUID, never publicId or another merchant ID.', so the description adds no parameter details beyond that. Baseline 3 is 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 states the tool reads one owned payment UUID, which is clear. It distinguishes it from list operations by emphasizing 'one owned' and 'UUID', but doesn't explicitly differentiate from other get tools like auraspay_ticket_get. Emphasis on reconciliation is a differentiator from listing tools, but it doesn't name a sibling that does something similar.

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 this tool is for reconciliation (when authoritative data is needed), but does not explicitly state when NOT to use it or mention alternative tools (e.g., use payments_list for listing). Provides some context that it's for authoritative reads, but not enough for an agent to know it's the right choice versus other get/list tools.

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