delete_observations

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 fails to disclose that deletion is permanent, irreversible, or the effect of partial matches (e.g., if some observations don't exist). It only states the action and matching requirement, leaving destructive side effects unaddressed.

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 brief and front-loaded, with two sentences that immediately state the purpose and then give the required input structure. No superfluous detail, making it easy to parse.

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 delete operation with a nested input, the description covers the input contract but omits behavioral specifics like idempotency, error handling, and whether the operation is atomic. Since an output schema exists, return values are not needed, but the destructive nature and edge cases are underexplained.

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 is minimal (one array of objects with no defined properties), so schema coverage is 0%. The description compensates by specifying the exact required fields (entityName as string, observations as list of strings with exact content match), adding essential meaning beyond the schema.

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 deletes specific observations from entities in a knowledge graph, with a specific verb ('Delete') and resource ('observations'). It distinguishes itself from sibling tools like delete_entities and delete_relations by targeting observations only.

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 provides clear context on what is needed: each deletion item must have entityName and observations with exact content match. It doesn't explicitly mention alternatives or when not to use, but the targeted phrasing implies it is for observations, not entities or relations, providing adequate usage context.

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