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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is largely conveyed. The description still adds real value by specifying what gets destroyed (both CAD and synthesis artifacts), that destruction is immediate, and that a signed CertificateOfDestruction with zero_retention_verified=True is returned. It does not cover authorization requirements or behavior when the job does not exist.

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?

One front-loaded sentence with the destructive action first and the return artifact second; nothing is padded or redundant.

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 single-parameter destructive tool whose annotations cover safety flags, the description covers action scope, immediacy, and the return artifact, so an agent knows what it gets back despite no output schema. It falls short on preconditions and permission/authorization context, which matter for an irreversible purge.

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% for the single job_id parameter, and the description adds no syntax, format, or scope detail beyond restating that the job is shredded. Baseline 3 applies when the schema carries the parameter semantics.

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 names a specific verb ('shred'), a precisely scoped resource ('all enclave CAD and synthesis artifacts for job_id'), and the immediate effect. No sibling tool operates on the enclave job vault, so the agent can distinguish it from reads like calligraphy_get_job_status without opening the 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?

There is no when-to-use or when-not-to-use guidance, no preconditions (e.g., whether the job must be completed or downloaded first), and no mention of alternatives such as downloading the fab bundle before purging. 'Immediately' hints at irreversibility but does not tell an agent when this call is appropriate.

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