List Alexa routines

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

With no annotations, the description carries the full burden. It states that the tool lists routines with certain fields, but it does not disclose any behavioral traits such as read-only nature, rate limits, ordering, pagination, or error conditions. The description is insufficient for an agent to understand all implications of calling this 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?

The description is extremely concise—two sentences that front-load the key information (fields returned) and then provide a usage example. Every sentence is valuable and there is no redundancy.

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 tool's simplicity (1 optional parameter, no output schema, no annotations), the description is adequate for basic understanding but has clear gaps. It lacks parameter semantics and behavioral details, which are needed for complete guidance.

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 description coverage is 0% for the single parameter 'limit'. The description does not mention the parameter at all, failing to add any meaning beyond the schema's type constraints. The agent has no guidance on how to use the limit parameter or its effect.

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 it lists all routines and specifies the returned fields (automationId, name, status, trigger types). It also provides a concrete use case (identifying a routine), and the tool is distinct from sibling tools like alexa_get_routine which retrieves a single routine.

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?

The description includes a usage guideline: 'Use this to identify a routine (e.g. a scheduled one that fires an unexpected scene)'. This provides clear context for when to use the tool, but it does not explicitly mention when not to use it or name alternative tools.

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