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

With no annotations, the description carries the full burden. It does disclose two genuinely useful behaviors: the submission is encrypted/anonymized and produces a signed receipt, and that resubmitting with the same agent_secret is idempotent (returns the original receipt rather than creating a duplicate). However, it says nothing about required attestations, permission or auth expectations, or what happens on partial/validation failure for an 18-parameter mutation.

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?

Two tight sentences, front-loaded with the core action and followed by the one non-obvious retry rule. No filler.

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 with 18 parameters, 9 of them required, no annotations, no output schema, and a challenge/solution pair that is never explained, the description is far too thin. An agent cannot tell what challenge and solution are, what the mandatory attestations require, or how release_mode affects the submission.

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 only 17% across 18 parameters, so the description must compensate and largely does not. It implies agent_secret functions as an idempotency key (useful, and not stated in the schema), but says nothing about challenge, solution, subject, category, severity, attestations, release_mode, or the evidence array.

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 compound action — encrypt an anonymous safety disclosure and return a signed receipt — which is a distinct purpose from siblings like submit_confession and decide_release. It doesn't name an alternative tool, but the resource and artifact (anonymous disclosure + signed receipt) make identification straightforward.

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 description gives no when-to-use guidance relative to submit_confession, decide_release, or verify_receipt. The only conditional statement is about retry behavior, which is a behavioral trait rather than a usage guideline.

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