list_timelines

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes what timelines contain (status, output, metadata) and their purpose, but lacks details about permissions, rate limits, error conditions, or pagination behavior beyond what's implied by 'list'. The description doesn't contradict any annotations since none exist.

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 perfectly concise with two sentences that each earn their place. The first sentence defines the tool's core function, while the second provides usage context. There's zero wasted language or 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?

For a read-only listing tool with 5 parameters and no output schema, the description is adequate but has gaps. It explains what timelines are and their purpose, but doesn't describe the return format, pagination details (beyond the nextToken parameter in schema), or error handling. With no annotations and no output schema, more behavioral context would be helpful.

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 100%, so the schema already fully documents all 5 parameters. The description doesn't add any parameter-specific information beyond what the schema provides (e.g., it doesn't explain relationships between workflowId and executionId or provide examples). The baseline of 3 is appropriate when the schema does all the work.

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 the tool's purpose with specific verbs ('list timelines', 'inspect individual step results', 'debug failures', 'see execution flow') and distinguishes it from siblings like 'get_timeline' (singular) by emphasizing it lists multiple step execution records for a specific execution. It explicitly identifies the resource as 'timelines (step execution records)'.

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 provides clear context for when to use this tool ('to inspect individual step results, debug failures, or see the execution flow'), but does not explicitly state when not to use it or name alternatives. It implies usage for post-execution analysis rather than real-time monitoring, though this could be more explicit.

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