delete_observations

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

No annotations provided. Description only details input format, not behavioral traits like destructiveness, permissions, or atomicity. Agent cannot infer side effects or error handling.

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?

Two succinct sentences: first states purpose, second details parameter structure. No redundant or irrelevant text. Ideal front-loading.

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?

Adequate but incomplete: explains input format but no behavior on success/failure, idempotency, or what happens if observations missing. Output schema exists, partially compensating for missing return value description.

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 coverage is 0%, so description compensates by specifying required keys (entityName, observations) for each dict in the deletions array, adding meaning beyond the permissive 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, with a precise verb and resource. It distinguishes from sibling tools like delete_entities, delete_relations, and add_observations.

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 guidance on when to use this tool versus alternatives (e.g., delete_entities for deleting entire entities). No exclusions or prerequisites mentioned.

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