merge_entities

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

No annotations provided; description discloses rewriting observations (destructive) and marking source merged, but does not clarify if source is deleted, permissions needed, or reversibility. Lacks detail for a write 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?

Single sentence, front-loaded with key action and effect. 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?

Given merge complexity and 0% schema coverage, description omits crucial details: what happens to source entity (deleted or hidden), constraints (same entity type?), and purpose of merge_reason. Output schema absent.

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 has 0% coverage; description does not explain any of the 4 parameters (from_entity_id, to_entity_id, merge_reason, user_id). Fails to add 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?

Clearly states action 'merge', resource 'entities', and effect 'rewrites observations from source to target and marks source as merged'. Distinguishes from siblings like split_entity.

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?

Explicitly says 'merge duplicate entities' which implies when to use. No comparative guidance against alternatives like split_entity, but clear enough.

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