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

With no annotations, the description carries the full burden, yet it only implies anonymity/encryption and a rule to retain a secret. It says nothing about what happens to submitted data, release modes, attestation consequences, required challenge/solution flow, or permissions.

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 short sentences, front-loaded with the core action, with no filler. The second sentence is cryptically worded but brief, so waste is minimal.

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 21-parameter tool with 9 required fields, nested objects, multiple enums, attestations and no output schema, the description is drastically under-specified. An agent cannot infer the submission protocol, required inputs, or side effects from it.

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 14% (just agent_secret, reputation_pubkey, reputation_signature), leaving most of the 21 parameters undocumented. The description adds no field-level meaning such as the challenge/solution requirement or the categories/attestations.

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 states a specific verb and resource ("Encrypt an anonymous confession") that maps to the tool name, so an agent can distinguish it from siblings like submit_leak. However, it does not explicitly differentiate from submit_leak or explain the encrypt-then-submit relationship.

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 relative to the many siblings (submit_leak, decide_release, flag_item). The second sentence ("early disclosure earns at least as much acknowledgment as completed acts") is a behavioural nudge, not an invocation criterion.

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