delete_observations

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

With no annotations, the description carries the full burden. It discloses the exact-content-match requirement for observations, which is a valuable behavioral detail, but does not mention side effects, error handling, or destructive consequences beyond the obvious delete operation.

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 exactly two sentences: the first fronts the purpose, the second provides parameter structure. Every sentence earns its place with no wasted words.

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 focused deletion tool with a single parameterized array, the description covers the essential structure and behavior. Return values are likely documented by the output schema, but the description does not mention preconditions (e.g., entity existence) or failure behavior.

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 highly generic (array of objects with additionalProperties true), with 0% schema description coverage. The description compensates fully by specifying the required nested fields (entityName and observations), their types, and the exact match semantics, adding significant 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 it deletes specific observations from entities in a knowledge graph, using the specific verb 'delete' and the resource 'observations'. This distinguishes it from sibling tools like delete_entities and delete_relations.

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?

No explicit when-to-use or alternative recommendations are provided. The description implies its usage through the focus on observations, but it does not mention any exclusions or contrast with sibling tools.

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