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

Annotations already declare the write/destructive/idempotent profile, so the remaining value is the disclosure of the concrete effect (the address becomes able to receive mail again) and the consent precondition, plus the DELETE /blockings/{email} operation. That adds real context beyond the structured fields, though it does not cover rate limits 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?

Three short sentences, each earning its place: the operation, the safety precondition, the endpoint. The action type is front-loaded so the agent sees it is a write immediately.

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 one-parameter mutation with rich annotations and no output schema, the description covers purpose, effect, precondition, and endpoint. Idempotency and destructiveness are already handled by annotations, so nothing an agent needs is missing.

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 0% for the single 'email' parameter, but the schema itself enforces the email format with a strict pattern. The description compensates where it matters by clarifying it operates on exactly one address, distinguishing this from any bulk variant.

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 verb ('remove') and resource ('one address from the account blocklist') plus the resulting effect ('so it can receive email again'). The singular 'one address' cleanly separates it from the sibling bulk tool emailchef_block_emails and from the read-only emailchef_list_blocked.

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?

Gives an explicit precondition: 'Only do this for an address whose owner asked for it,' which tells the agent when the call is appropriate. It does not name a sibling alternative or exclusion cases (e.g., blocked-by-system addresses), so it falls short of a 5.

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