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

Annotations already cover the safety profile (readOnly=false, destructive=false, idempotent=true). The description adds the crucial behavioral context that this is a human-consent-gated action and must not be invoked autonomously, which is beyond what the annotations convey. It stops short of describing the response or failure modes.

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 precondition and then the value to send, with the safety warning last. No filler or redundancy.

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 simple one-required-parameter consent tool with annotations covering idempotency and safety, the description covers the key facts an agent needs: when to call it and what to send. Absence of return-value detail is acceptable since no output schema exists, though a note on success/failure behavior would complete 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 coverage is only 50% (agent_key is documented, accepted_terms has no schema description), but the description compensates by specifying the exact value to send (accepted_terms: true), matching the const constraint. It adds meaning the bare schema does not.

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 action (accepting the participation terms) and ties it to a concrete URL, so an agent knows exactly what the tool does. It doesn't explicitly contrast with siblings like enroll or leave_network, but the purpose is unambiguous.

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?

It states the precise precondition (only after the person has read and agreed to the terms) and an explicit prohibition ("Never accept without asking them"). This is a clear when-to-use plus a when-not-to-use, which is rare and valuable for a consent-gated action.

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