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

Goes well beyond the readOnly/idempotent/destructive annotations by declaring negative capabilities that an agent would otherwise guess wrong: no score, no pass/fail, no status, runs no model, fetches nothing, stores nothing, deterministic outputs, not legal advice or conformity assessment. This directly prevents misuse of the returned checklist as a certification result.

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?

Front-loaded with the verb, resource, and scope, and the middle section usefully describes the return payload. The final sentence and repeated disclaimers are somewhat dense, but each disclaimer guards against a concrete misinterpretation, so very little is pure waste.

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 an output schema present, the description still usefully summarizes the four returned fields, and it covers determinism, side-effect profile, and disclaimer boundaries. Nothing an agent needs to call it correctly or interpret the result is missing.

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 schema already documents all three parameters including the enum. The description adds only light value: it reiterates the nine framework values and clarifies that sector is advisory and role is echoed, which is already largely stated in the schema text.

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 artifact (a deterministic readiness checklist) over a named set of nine governance frameworks, and enumerates the exact per-item payload (provision, plain-words summary, evidence, open question). An agent can distinguish this from sibling verification/axis tools without opening any schema.

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 use case is implied clearly ('what evidence would be measured' for readiness), and the optional sector/role semantics are spelled out. However, it never names an alternative sibling (e.g. axis_conformance, axis_regulatory-framework) or states when-not-to-use-this-vs-that, so routing is left to inference.

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