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

Annotations declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the safety profile is partly covered. The description adds nothing beyond that: it does not say whether state is mutated, what credentials are needed, or why a supposedly read-like 'audit' is flagged as not read-only. 'Proof-ready decision context' conveys no verifiable behavior.

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?

It is a single short sentence, so there is no bloat, but half of it is spent on the meaningless phrase 'proof-ready decision context'. Concise in form, under-specified in substance.

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 tool whose only input is an opaque JSON body deferred to an external schema, and with no output schema to describe the return value, the description should explain what is audited and what comes back. It leaves the agent unable to predict either the input contract or the output.

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?

There is only one optional parameter and the schema provides a description for it (100% coverage), so the baseline of 3 applies. However, that schema description merely defers to an external 'AffixIO OpenAPI schema resource' rather than defining the body contract, and the tool description does not compensate for that deferral.

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 is essentially a restatement of the title ('Audit an edge payload'), padded with the undefined jargon 'proof-ready decision context'. Neither 'edge payload' nor what the audit actually examines is explained, and it does nothing to separate this tool from edge_catalogue, edge_reject_pii, affix_merkle_audit, or affix_agent_trust_audit.

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 guidance, no prerequisites, and no mention of any alternative. With four audit-flavored siblings and two other edge_* tools in the list, an agent has no basis for choosing this one over them.

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