add_observations

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

With no annotations provided, the description carries the full burden. It discloses the required input fields but does not explain what happens if an entity doesn't exist, whether the operation is atomic, or any side effects beyond adding observations. For a mutation tool, this is a significant gap.

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 sentences: the first states the purpose, the second provides the required item structure. There is no redundant or filler content, and the key information is front-loaded.

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?

The description is minimally viable for a simple add operation with one parameter, and it clarifies the input structure well. However, it does not address error handling, prerequisites (entity existence), or success confirmation, which an agent would likely need. Since an output schema exists, return values are not necessary, but the absence of behavioral edge cases keeps it at a 3.

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 schema only defines an 'observations' array with generic objects (additionalProperties true), so without the description, the required fields are unknown. The description fully compensates by specifying 'Each item must have: entityName (str), contents (list[str])', giving essential type and structure information.

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 uses a specific verb ('Add') and identifies the resource ('new observations to existing entities'), which clearly distinguishes it from sibling tools like delete_observations and create_entities. It is unambiguous about what the tool does.

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 implies usage by stating 'Add new observations to existing entities' but does not explicitly mention when to use it instead of alternatives. It provides context (existing entities) but no explicit when-not-to-use or prerequisites beyond that, so it falls short of a strong recommendation.

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