ListFISExperiments

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

With no annotations, the description carries the full burden. It helpfully discloses scope (current account and region) and that pagination is handled automatically, plus the return shape. However, it omits authorization requirements, rate limits, and error behavior, which matters for an unannotated 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?

Front-loaded with the core action, then scope and pagination in a compact second sentence. The 'Returns:' block is somewhat redundant for a simple dict but not wasteful enough to penalize heavily.

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?

There is no output schema, but the description compensates by explaining the return value (a dict of experiment details organized by name). For a zero-parameter read tool with no annotations, this covers the essentials an agent needs, though permission/error context is absent.

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, so the schema cannot be improved upon and the baseline of 4 applies. The description correctly indicates no filtering arguments are needed.

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 ('Retrieves a list of') and resource ('Experiments') within AWS FIS, and the scope (current account and region) is clear. It implicitly distinguishes itself from GetFISExperiment (singular) via the plural 'list', though it never names siblings explicitly.

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?

Usage is implied by the listing framing, but the description gives no explicit when-to-use guidance or exclusions relative to siblings like GetFISExperiment or ListFISExperimentTemplates. The agent must infer that this is the bulk-listing option.

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