devbook_delete_attachment

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

No annotations are supplied, so the description carries the full burden. "Purge" hints at permanent, irreversible removal, but nothing states whether the deletion is recoverable, whether it requires ownership or specific permissions, what happens if the attachment_id does not exist, or whether the parent prompt is affected.

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?

A single short, front-loaded sentence with no filler. "Purge and delete" is mildly redundant, though the doubling arguably signals permanence rather than wasting space.

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 simple two-parameter tool whose schema is fully annotated, the description covers the core action adequately. It falls short on the behavioral side—irreversibility, error conditions, and interaction with the parent prompt—which matters for a destructive operation with no annotations.

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%, with both prompt_id and attachment_id fully documented in the schema, so the baseline is 3. The phrase "from a prompt" loosely maps to prompt_id but adds no format, constraint, or behavioral detail beyond what the schema already provides.

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 pairs a specific verb ("Purge and delete") with a specific resource ("an attachment from a prompt"), so an agent knows exactly what operation is performed. It does not name or distinguish itself from siblings such as devbook_delete_prompt or devbook_upload_attachment, leaving that differentiation to the tool name alone.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no warning about when not to call it. The agent must infer from the name alone that this is the removal counterpart to devbook_upload_attachment and that prompt-level deletion belongs to devbook_delete_prompt.

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