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

The description explicitly states 'Read-shaped tools only' and implies this tool is read-only, while the annotations declare readOnlyHint=false. This is a direct contradiction about the tool's mutation behavior, and no other behavioral traits are disclosed.

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 includes irrelevant server details and a URL, and the main purpose is buried under extraneous text. It is not front-loaded effectively, and the truncated sentence adds confusion rather than 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?

With no output schema, no defined parameters, and a description that fails to explain inputs or behavior clearly, the tool is severely under-specified. An agent would not know how to invoke it correctly or what it returns.

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?

Despite having zero defined parameters, the description attempts to mention 'Takes the transaction si' but is incomplete and vague. It does not clarify what input is expected, leaving the agent without adequate guidance for a tool with an open schema.

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 that the tool proves from the chain that a payment met the demand it answered, which is a specific verification purpose. However, it is muddled by unrelated server-level context and a truncated phrase ('Takes the transaction si'), reducing clarity.

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?

It mentions the tool operates 'read-shaped' and that the payee's word is not relied upon, giving some context, but it does not specify when to use this versus alternatives, nor does it state exclusions or prerequisites beyond the general read-only note.

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