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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds value beyond that by disclosing cost (0.004 USDC) and behavioral properties (deterministic, evidence-bounded, signed) that the annotations do not carry. It stops short of saying what the binding produces or what authority constraints mean operationally, so a 5 is not warranted.

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 short and front-loads the core action before the price and property fragments. Structure is slightly harmed by telegraphic fragments and odd punctuation ('authority.; 0.004 USDC.'), which read as clipped slogans rather than complete statements, but 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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. What is missing is the operational role: with a permissive input schema and 28 closely related payment siblings, the agent still cannot tell what inputs to bind or when this gateway is the correct choice. Adequate but with a real routing gap.

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?

The tool declares 0 named parameters (schema is a permissive object with minProperties 1 and additionalProperties true), so per the baseline this scores 4. The schema example hints at source.id / transaction.id shapes, and the description adds nothing to that, but with no properties to document the description is not obliged to compensate.

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 object — 'Bind an MCP tool call to transaction evidence' — plus a scope qualifier ('without granting undeclared authority'), so an agent can form a rough idea of the operation. However, it never differentiates itself from the large set of payment/transaction siblings (transaction_assurance, a2a_transaction_bridge, preflight, etc.), so an agent has no way to know why this gateway rather than those. Clear enough to score 4, but the missing sibling contrast blocks a 5.

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?

There is no when-to-use statement, no precondition, and no named alternative despite 28 sibling tools in the same payment/transaction domain. The only contextual cue is the '0.004 USDC' price fragment, which implies a paid call but does not tell the agent when to route here versus a2a_transaction_bridge or transaction_assurance. Effectively no usage guidance.

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