revise_all

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

Discloses partial update semantics and atomicity. With no annotations, description carries full burden; missing details like error handling when an ID doesn't exist, rate limits, or required permissions.

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, no filler. Action and key constraints (atomicity, partial updates) 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?

Covers essential points for a batch update tool: atomicity and field behavior. Lacks information on maximum array size, ordering guarantees, or error scenarios, but adequate for a simple tool with no output schema.

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 100% and already explains the 'updates' parameter structure. Description adds minimal value beyond noting only provided fields change, which is implicit from optional fields in 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?

Clear verb 'Update' with specific resource 'multiple existing memories' and transactional behavior. Distinguishes from sibling tools like 'revise' (single) and 'remember_all' (create multiple).

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 states transactional behavior ('all succeed or roll back') which guides when to use. Lacks direct comparison to alternatives like 'revise' for single updates.

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