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

With no annotations provided, the description carries the full burden of behavioral disclosure. It merely states the package composition and does not disclose whether the tool is read-only, whether it verifies existing proofs or creates new ones, what side effects occur, or what the output format is. This is a significant transparency gap.

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 structurally clear with a colon separating the package concept from its components, and there is no redundant wording. However, it is under-specified to the point of being nearly a label, sacrificing essential information for brevity. It is not as sparse as 'Process' but still leaves too much unsaid.

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 that packages three different proof types, the description is incomplete. It does not explain the workflow, the role of entity_id, what 'auditor-ready' means operationally, or what the caller should expect. The absence of annotations and output schema makes this incompleteness more damaging.

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 schema defines a single parameter entity_id with no description, and the tool description does not mention it at all. Schema description coverage is 0%, so the description was expected to compensate, but it provides zero insight into what entity_id means or how it impacts the proof package.

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 identifies the tool as an 'auditor-ready proof package' and lists its components (commitment + merkle + credential), which indicates what it produces. However, it lacks an explicit action verb (e.g., generate, create, assemble) and does not clearly distinguish this from sibling proof-related tools like obligation_proof or threshold_proof.

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 guidance on when to use this tool versus alternatives. The phrase 'auditor-ready' hints at an auditing use case, but no alternatives are named and no exclusions or context are provided. The description gives no actionable direction for an agent deciding between this and create_commitment, build_merkle_tree, or other proof tools.

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