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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds genuinely new outcome detail beyond the annotations: the inbox URL returns 404 and the inbox_key becomes invalid, which tells the agent the deletion is effectively irreversible.

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, no filler, and the destructive outcome is front-loaded rather than buried. Every clause carries information an agent needs before calling a delete.

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?

An output schema exists, so return values need not be explained, and the description covers the irreversible consequence of the call. The only gap is the absence of prerequisite/authorization context, though openWorldHint=false and the annotation set largely frame the operation.

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?

Only one parameter, and the schema already carries a 100% coverage description including the 'porch_sk_' prefix origin. The description adds nothing about inbox_key, so the baseline 3 applies when the schema does all the work.

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?

'Delete the inbox and everything it captured' states a specific verb plus resource and quantifies the blast radius (the inbox and all captured content). It is unmistakably distinct from create_inbox, get_inbox and clear_requests, which cover other lifecycle stages.

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 description gives no when-to-use or when-not-to-use guidance and never mentions the neighboring clear_requests tool, which removes requests without destroying the inbox. An agent must infer the decision criteria from the tool name alone.

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