alexa_remove_list_item

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

Annotations already declare destructiveHint and openWorldHint, but the description adds the concrete consequence (quantity or note on the item is lost) and fully documents the confirmation protocol, including that the first call may only return a preview plus confirmToken. That is substantial context beyond the structured fields.

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?

Front-loads the action, then the destructive warning, then the confirmation mechanics in a compact three-sentence flow. Every clause earns its place and the highest-risk information arrives early.

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?

Even without an output schema, the description explains what phase 1 returns (a preview and a confirmToken) and under which client conditions, so an agent can handle either confirmation path correctly. Nothing essential for a destructive three-parameter tool is missing.

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%, so the baseline is 3, and the schema already documents list, item, and confirmToken. The description adds routing value by tying item ids to alexa_get_list_items and reiterating that the token must never be invented or reused, which reinforces the schema's guidance rather than merely restating it.

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?

States a specific verb (Delete) and resource (an item from an Alexa shopping or to-do list) and immediately distinguishes itself from the update/add siblings. An agent can tell it apart from alexa_update_list_item or alexa_add_list_item without opening a schema.

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?

Names the accepted identifier sources (item name or item id from alexa_get_list_items, list id from alexa_list_lists) so the agent knows the prerequisite calls. It also states the exact confirmation branch conditions (elicitation-capable client vs. two-step token fallback), leaving nothing to inference.

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