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

Adds substantial behavior beyond the annotations: 'Full account key required' (auth requirement), 'Does not automatically increase limits or resume sending' (no side effect on sending state), 'Three requests per day' (rate limit), and 'repeated pending requests keep the original purpose' (refines the idempotentHint). These are exactly the operational facts an agent needs before calling, and none repeat the structured fields.

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?

Four short sentences, front-loaded with the action, then constraints. Every clause carries a distinct operational fact (auth, effect, rate limit, idempotency) with 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 one-parameter submission tool with no output schema, it covers auth, rate limits, side effects, and repeat behavior well. The one gap is that it does not say what a call returns (e.g., a review reference or status) for the agent to track the request.

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% and the single 'purpose' parameter is fully documented in the schema, including length bounds and the 'no secrets or private messages' caveat. The description adds no further meaning to the parameter itself, so baseline 3 applies.

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 and resource ('Request an operator review of your sending purpose and recipient consent'), which is clearly distinct from siblings like send_email, check_sending_status, or register_agent. An agent can tell this is a human-review escalation, not a sending or status action.

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 'request an operator review of your sending purpose and recipient consent' phrasing plus 'Does not automatically increase limits or resume sending' implicitly tells the agent this is the escalation path and not the limit-increase tool. It stops short of naming explicit alternatives or stating preconditions for filing a request versus using check_sending_status.

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