list-update

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

The word 'Updates' implies modification, but no details are given about idempotency, side effects, required permissions, or error handling. With no annotations, the description should provide more behavioral context.

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 very short (one sentence plus a tag). While concise, it omits necessary details, so it is not optimally informative.

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 the nested object parameter and no output schema, the description is insufficient. It does not explain the effect of the update, the structure of requestBody, or constraints like required fields, making it incomplete.

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?

Only requestBody has a trivial description ('The JSON request body'), and listPublicId lacks description. The schema coverage is 50%, but the description adds no new meaning beyond the schema, failing to compensate.

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 action ('Updates a list') and identifies the list by public ID. Among siblings like list-create and list-delete, the purpose is distinct, though no explicit sibling differentiation is provided.

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., list-create, list-delete). No preconditions or restrictions are mentioned, leaving the agent to infer usage context.

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