Delete Observation Item

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

Annotations already mark the tool as destructive (destructiveHint=true). The description adds value by specifying the 'recycle bin' mechanism and repeating that the action 'cannot be undone,' reinforcing permanence. It also provides the API endpoint for reference. No contradiction with annotations.

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 somewhat repetitive, stating 'permanently delete' and 'cannot be undone' twice each. While it is relatively short, it could be more concise without losing clarity. The API endpoint info is extra but not essential for tool selection.

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's simplicity and rich annotations, the description covers the essential: destructive action, required parameters, and API details. However, there is a minor inconsistency between 'sends to the recycle bin' and 'permanently delete,' and no information about return values or pagination is provided. Adequate but not outstanding.

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 100% coverage with clear descriptions for both parameters (project_id and id). The description merely restates that they are required, adding no new meaning. Baseline of 3 is appropriate since the schema already does 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?

The description clearly states the tool sends an Observation Item to the recycle bin and permanently deletes it, with specific verbs 'delete' and 'remove'. It identifies the resource (Observation Item) and lists required parameters, effectively distinguishing it from non-destructive siblings like 'show_observation_item' or 'update_observation_item'.

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 says 'Use this to permanently delete the specified Observations,' which indicates when to use the tool. However, it does not explicitly mention when not to use it or suggest alternatives such as soft delete or updating instead. The context of sibling tools helps, but direct guidance is lacking.

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