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

The description reveals that the tool verifies an externally broadcast payment (not initiated by this tool) and continues a job, adding context beyond the annotations. The annotations already indicate idempotency (idempotentHint: true) and non-destructive (destructiveHint: false). The description does not contradict annotations and adds useful behavioral nuance about the separate broadcast step.

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 two sentences: the first states the purpose, the second provides instructions on what to provide. Both are front-loaded with essential information. No superfluous words, and every sentence adds value.

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?

Given the tool has 5 parameters (4 required, one nested object) and an output schema exists, the description covers the main inputs and prerequisite. However, it does not explain error handling, what happens if verification fails, or the overall flow beyond the immediate step. The confusing mention of 'walletPayment' (not in schema) also detracts. Adequate but not thorough.

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 only 40% (2 of 5 params have descriptions). The description adds meaning for three parameters: job_key ('same job_key' implies matching the quote), payer_address (from broadcast), and transaction_hash (from broadcast). It does not mention notify_email, and there is a confusing mention of 'walletPayment' which is not in the input schema. The description partially compensates for low schema coverage but is incomplete.

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 clearly states the specific action: verifying a separately broadcast Tempo mainnet push-mode payment and continuing the quoted research job. It references the prerequisite tool (a9n9_research_quote) and lists the required inputs (transaction hash, payer address, job key). This distinguishes it from sibling tools like a9n9_research_quote or a9n9_research_start, which are different steps in the workflow.

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 explicitly tells the agent to use the paymentChallenge and walletPayment from a9n9_research_quote, establishing a clear prerequisite. It implies this tool should be used after quoting and before continuing the job. However, it does not explicitly state when not to use it or mention alternatives, which would make it stronger.

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