List Homeric Atlas episodes

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

Annotations already mark the tool as read-only, idempotent, and non-destructive. The description adds useful behavioral context beyond those flags: it returns every episode, in a deterministic reading order, with completeness implied by 'every' and aligned with the `openWorldHint: false` signal. There is no contradiction with annotations.

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?

Two sentences deliver the core action, the result contents, the ordering behavior, and the routing to the sibling tool. Each clause earns its place, and the primary purpose is front-loaded in the first sentence.

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 simple list operation with one optional and fully described parameter, an output schema available, and annotations covering safety, the description is complete. It tells the agent exactly what the list contains, how it is ordered, and how to proceed if detail is needed.

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 single parameter `locale` is fully documented in the input schema, including its enum values and default behavior. The description adds no parameter-level detail, but none is needed because the schema already covers 100% of parameter semantics.

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 names a specific verb ('List'), a specific resource ('every episode of the Iliad and the Odyssey held in the atlas'), and defines the output shape: reading order, passage, places, and locatability. It also explicitly distinguishes itself from `get_homeric_episode`, so an agent can tell the list operation from the detail operation without inspecting schemas.

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 gives direct selection guidance: 'Use this to find the episode you want; use `get_homeric_episode` for its theories and sources.' This tells the agent both when to choose this tool and when to choose the sibling alternative, which is explicit and actionable.

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