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 safety profile is covered. The description adds the default limit and the return shape ({payments: [...], count: N}), which is useful, but it doesn't disclose pagination behavior beyond the limit parameter or clarify what 'matched' means in terms of matching state. No contradiction with 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 compact and front-loaded with the core purpose, followed by parameter details and return shape. Every sentence earns its place, though the Args/Returns formatting is slightly verbose for a simple two-parameter tool.

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 list tool with two optional parameters and no output schema, the description covers the essentials: what it lists, the filters, and the return shape. It doesn't explain the meaning of 'matched' debt payments or how this relates to the debt payment matching workflow, which could matter for an agent deciding between this and confirm_debt_payment_match.

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 carry the parameter meaning. It does explain status values (pending, confirmed, rejected) and limit defaults (20, max 200), which adds value beyond the bare schema. However, it doesn't specify the exact accepted status string format beyond the examples, and the schema itself has no enums, so there is some ambiguity.

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 specific verb and resource ('List matched debt payments') and enumerates the status filter values, which distinguishes it from related tools like list_debt_payment_rules and confirm_debt_payment_match. It doesn't explicitly name a sibling to differentiate from, but the scope is clear enough.

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 usage by listing the status filter and limit, but it doesn't explicitly state when to use this tool versus alternatives like list_payment_history or confirm_debt_payment_match. There is no when-not-to-use guidance, so an agent must infer the context from the name and sibling list.

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