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

Annotations carry the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the agent knows this mutates state and is not idempotent. The description adds nothing beyond the endpoint path: it does not say what the audit records, whether re-running has side effects, or what auth is required. Note the mild tension between the read-sounding verb 'audit' and readOnlyHint=false, but this is not a direct contradiction.

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?

A single front-loaded sentence with no filler; the purpose leads. The trailing endpoint path is slightly redundant but serves as a useful anchor.

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 state-mutating operation with no output schema and a request body whose contract is deferred to an external resource, the description does not tell the agent what a receipt looks like, what the audit produces, or what side effects to expect. It is too thin given this complexity.

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%, so the single 'body' parameter is documented in the schema, but only by deferring to 'the AffixIO OpenAPI schema resource for the contract.' The description adds no field-level or format meaning, so the high-coverage baseline of 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+resource: auditing a single verification receipt against the Merkle audit tree, and the '(POST /v1/merkle/audit)' anchor pins the operation. The word 'single' lightly separates it from the sibling affix_merkle_audit_batch, though the differentiation is implicit rather than stated.

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 explicit when-to-use guidance, but 'single' implies the batch sibling (affix_merkle_audit_batch) is the alternative for multiple receipts. The condition that selects this tool is only implied, not stated.

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