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

Annotations cover the safety profile (write, idempotent, non-destructive), and the description goes further by disclosing that the dismissal is scoped to the current offer set and won't carry over to later sources. It also documents the billing-refusal path (BILLING_INACTIVE / MONTHLY_CAP_REACHED), the `tellHuman` field, and that an owner must resolve it — genuinely useful behavior beyond the annotations.

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?

Purpose is front-loaded, but the prose is padded with rhetorical emphasis ('PASS IT TO YOUR HUMAN', 'do NOT absorb the refusal') and repeats the 'answer on their behalf' idea. The billing content earns its place; the redundant exhortation does not.

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 zero-param write tool with no output schema, the description covers purpose, consent condition, persistence scope, and failure handling. It omits what a successful response looks like, which is the one remaining gap.

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?

The tool takes zero parameters, so there is nothing to document; baseline for 0-param tools is 4. The description does not waste space re-explaining absent inputs.

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 gives a concrete semantic action: record that none of the currently offered placeholders are the agent's human. This implicitly contrasts with the 'yes' path (claim_ghost / claim_issue), so an agent can differentiate it, though the jargon ('placeholders', 'ghost prompt') is obscure and only fully decodable from the tool name.

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?

"Call it only when they have said so — it is an answer on their behalf either way" gives an explicit when-to-call condition and a consent caveat. The scope clause about covering only currently offered source tools adds clear boundaries, but no sibling alternative is named by name.

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