alexa_list_lists

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered without the description. The description adds one useful behavioral fact beyond that: the output includes a count of active items per list. It says nothing about auth requirements, rate limits, or account-scoping behavior, which is acceptable given the annotations but not additive beyond payload shape.

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?

A single sentence with no filler. The core action and scope are front-loaded, and the one extra clause (item counts) earns its place by describing the return payload in the absence of an output schema.

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?

For a zero-parameter read operation whose annotations already cover the safety profile, the description is nearly sufficient: it names the resource and hints at the return shape. With no output schema, it could go one step further and mention the identifiers/names returned that feed alexa_get_list_items, but nothing needed to invoke it correctly 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?

The tool takes zero parameters and the description correctly introduces no non-existent arguments, so there is nothing to mis-document. Baseline for a zero-parameter tool is 4; there is no argument syntax the description could meaningfully add.

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?

Specific verb ("List") plus a precisely scoped resource ("shopping and to-do lists on the account"), and it even discloses the payload detail of per-list active item counts, which no sibling provides. It is not confused with alexa_list_devices, alexa_list_routines, or alexa_list_volumes. However it never explicitly contrasts itself with alexa_get_list_items, the closest sibling, so it stops short of full sibling differentiation.

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?

There is no explicit when-to-use statement, no prerequisites, and no named alternative. Usage is only implied by the surrounding toolset: an agent can reasonably infer this is the discovery call that precedes alexa_get_list_items. Adequate but leaves the ordering/allowed-argument context to inference, since get_list_items probably needs a list identifier that must come from here.

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