delete_inbox

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

No annotations provided, and the description does not disclose behavioral traits like whether deletion is permanent, cascading effects, or required permissions. It only states the action 'Delete an inbox' without context.

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?

The description is very short, but the 'Args' block largely duplicates the schema and adds no new information. It is concise but not optimally structured; the parameter list could be omitted since the schema already defines them.

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?

Given the tool deletes an inbox, the description should mention permanence, required permissions, and what the output schema contains. It does not, leaving the agent underinformed. An output schema exists but is not described.

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%; the description lists parameters with phrases like 'The domain ID' and 'The inbox ID to delete', which add minimal meaning beyond the schema titles and property names. No format, constraints, or examples provided.

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 clearly states 'Delete an inbox' – a specific verb with a specific resource. It distinguishes from sibling tools that act on different resources (e.g., list_inboxes, create_inbox).

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?

No guidance on when to use this tool vs alternatives, no prerequisites (e.g., need domain_id and inbox_id must exist), and no mention of when not to use it.

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