update_list

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

Discloses partial update ('Only the provided fields change') and return value. However, no annotations exist, and description does not cover permissions, side effects, or error conditions, leaving gaps for a mutation tool.

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 efficient sentences, each carrying essential information: purpose and behavior. No redundant 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?

Adequate for a straightforward update operation, but given 8 parameters and no output schema or annotations, could benefit from more detail on validation, prerequisites, or response structure.

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?

Input schema has 100% description coverage, so baseline is 3. Description merely lists parameter names without adding new semantics or constraints beyond what the schema already provides.

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?

Description uses specific verb 'Update' and resource 'List', lists the modifiable fields, and clarifies partial update behavior. This clearly distinguishes it from sibling tools that update other entities like tasks or folders.

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?

Implied usage context (when to modify a list), but lacks explicit when-not-to-use or alternatives. No comparison with similar update tools like 'update_task'.

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