update_assumption

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

No annotations are provided, so the description carries the full burden. It discloses batch behavior, the requirement for id in single mode, and the return confirmation. However, it does not state whether omitted fields are preserved or overwritten, nor does it describe error behavior for invalid or missing ids.

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 well-structured and front-loaded with the core purpose and batch support. It includes a redundant Args list that repeats schema information, but the sectioned format makes it easy to scan. It is slightly verbose but not excessively so.

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 covers the main modes, parameters, and return value. It does not discuss edge cases like what happens if neither id nor items is provided, or if a field must be present. However, the output schema exists, and the tool is moderate in complexity, so the description is largely sufficient.

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 covers 100% of parameters, so the baseline is 3. The description adds value by clarifying that id is required for single item mode and that each batch item must include id, which helps disambiguate usage. It also explains the difference between single and batch parameter handling.

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 'Update an existing assumption' with a specific verb and resource, distinguishing it from sibling tools like add_assumption, list_assumptions, get_assumption, and delete_assumption. It also notes batch support, further clarifying the tool's scope.

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 provides clear context for two usage modes: single item (provide id and fields) and batch (provide items list with ids). It does not explicitly exclude alternatives, but the purpose is distinct enough that an agent can infer when to use it.

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