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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered by structured data. The description adds only the HTTP route; it says nothing about error behavior for invalid tokens or the shape of the returned deposit, which for an openWorld API tool would be valuable.

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?

Two terse fragments, front-loaded with the resource identity and followed by the endpoint; every word carries information and nothing is padded.

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 single-parameter read with fully documented schema and annotations covering safety and idempotency, the definition is nearly sufficient. The only gap is that with no output schema, nothing hints at the deposit fields returned, though this is minor for a straightforward lookup.

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% and the deposit_token parameter already documents the dpo_ prefix and an example value, so the description's 'dpo_...' restates schema content. Baseline 3 applies.

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?

States a specific verb and resource ('One deposit by token') plus the underlying endpoint GET /deposits/{token}, so the retrieval semantics are unambiguous. 'By token' implicitly contrasts with the list_deposits sibling, but no sibling is named explicitly.

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 singular 'one deposit by token' implies this is the lookup path versus pinpayments_list_deposits, but the description never states when to use this instead of the list tool or how to obtain a token. Usage is inferable rather than declared.

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