delete_notification

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

No annotations are provided, so the description carries the full burden. It discloses the permanent deletion nature and the mutation aspect, plus the confirm requirement. However, it lacks details on effects, reversibility, or permissions beyond what is implied.

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 a single efficient sentence that front-loads the action and includes necessary execution constraint. No extraneous text.

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 no output schema and 7 parameters, the description is insufficient. It fails to explain why pagination/filtering parameters exist in a delete-by-id tool, leaving the agent confused about proper usage. The mutation tag and confirm note are helpful but incomplete.

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%, setting baseline at 3. The description adds the confirm parameter's role, but does not clarify the purpose of limit, offset, filter, type, agent_id, which seem unrelated to deleting a single notification. This creates ambiguity.

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 it deletes a notification permanently, with the verb 'Elimina' and resource 'notificacion'. It distinguishes the action as a mutation. However, it does not differentiate from sibling delete tools for other resources.

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 mentions the need for a confirm parameter to execute, but provides no guidance on when to use this tool versus alternatives like 'mark_notification_read' or other delete tools. No context on prerequisites or exclusions.

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