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

Annotations already declare readOnlyHint and non-destructive, so the bar is lower; the description still adds ordering guarantee, the returned field set, and an auth requirement (Cotlet API key with access to this app). No pagination or result-size behavior is disclosed, keeping it below 5.

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-loads purpose, then routing, then filter, then auth in a compact block with no filler. Minor redundancy between 'Steps of a trip in order' and 'Lists the steps of one trip in the order of the trip'.

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?

With no output schema, the description compensates by enumerating returned fields and ordering, plus the auth prerequisite. An agent has enough to call it correctly; only pagination/limit behavior is unaddressed.

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 coverage is 100%, so both parameters are already documented. The description's 'Pass since to see only steps from a given date' simply restates the schema's since description and adds no format or semantic nuance beyond it. Baseline 3 applies.

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?

Names a specific verb (Lists), resource (steps of one trip), and even enumerates the returned fields (place, country, date, title, photo count). It distinguishes itself from the sibling get_step by stating the latter returns full text, coordinates and photo links.

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?

Explicitly routes the agent: 'Story is a short preview; get_step returns the full text, coordinates and photo links,' and notes the since filter for date-scoped retrieval. Lacks an explicit when-not statement (e.g., vs list_trips), so it falls short of a full 5.

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