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

With no annotations, the description fully carries the disclosure burden and does so well: it states the payment is stored on the user's record, affects their score, generates a confirmation link to the business, and grants additional score weight only after confirmation. It also explicitly discloses that sensitive card numbers, account numbers, and keys are stripped before saving.

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?

Four sentences, all information-bearing and front-loaded. The core action is the first clause, and every subsequent sentence adds a distinct behavioral fact (no connection needed, score impact, confirmation link, data privacy) without repeating schema content.

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 tool with 8 parameters, nested objects, no annotations, and no output schema, the description covers the what, why, and consequences. It does not explain the response/return value or the confirmation-link mechanics in detail, but those are not required for selecting and invoking the tool correctly.

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 75%, so the schema already documents most parameters with meaningful descriptions. The tool description adds general context (record, score, confirmation link, data stripping) but does not add per-parameter meaning beyond the schema, so a 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 opens with a specific verb and resource: 'Write down a payment you already made,' and immediately broadens scope with 'anywhere: a bank transfer, a card, any payment app, any supplier's portal.' It clearly distinguishes the tool as a manual record-keeping action rather than a connected or initiated payment, and the sibling list contains no other tool with this exact record-a-completed-payment function.

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?

Usage context is explicit: this is for payments already made, and 'We do not need to be connected to it' tells the agent connection is not a prerequisite. It does not name a specific sibling alternative or an explicit 'do not use when...' condition, so it stops short of full when/when-not guidance.

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