delete_event_occurrence_attachment

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

With no annotations provided, the description fully carries the burden of behavioral disclosure. It explains that 'event_id' accepts multiple reference forms and is resolved to UUID, that 'att_id' is an attachment ID passed through unresolved, and states the return value {'ok': true}. This gives a clear understanding of the tool's behavior.

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 well-structured with a clear purpose statement first, followed by parameter details. It is efficient but could be slightly more concise by combining the two parameter paragraphs into one. Overall, it earns its sentences.

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?

The tool has three required parameters, no annotations, and no output schema provided (though description states return value). The description covers purpose, parameter handling, and return value, but the missing explanation for the 'date' parameter reduces completeness.

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 input schema has 0% description coverage, so the description must compensate. It explains 'event_id' reference resolution and 'att_id' semantics, but fails to describe the 'date' parameter, leaving a gap for one of three required fields.

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 a single attachment from an event occurrence.' It specifies the verb 'delete', the resource 'attachment', and the context 'event occurrence', which distinguishes it from sibling tools like 'delete_event_occurrence_comment' or 'delete_task_attachment'.

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 lacks any guidance on when to use this tool versus alternatives. It does not mention when not to use it or provide context about choosing between similar delete tools for different resources.

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