update_item_amount

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

No annotations provided; description only states the action. Does not disclose whether update is destructive, permissions needed, or behavior for invalid items. Lacks 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?

Very concise: one sentence for purpose and a parameter docstring. No unnecessary text, though could be slightly more informative. Efficient for its length.

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?

Simple tool with 3 required params, no output schema, no annotations. Description covers param semantics but lacks side effects, error handling, or return value info. Adequate for a basic update but not fully complete.

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 has 0% description coverage, but the description explains each parameter: list_id and item_id as numeric IDs, amount as a string with example. Adds meaning beyond the schema's type and title.

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 clearly states 'Update the amount of an item in a shopping list' with a specific verb and resource. It distinguishes itself from sibling tools like 'mark_item_purchased' or 'delete_item'.

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 like 'add_item' or 'mark_item_purchased'. There is no mention of prerequisites or exclusions.

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