stays

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

With no annotations, the description carries the burden. It discloses the chronological ordering and the output fields. However, it doesn't mention potential grouping behavior when the 'by' parameter is used, nor any default period or timezone considerations.

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, front-loaded with the main purpose and followed by a concrete use case. Zero filler.

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 tool with 7 parameters and no output schema, the description explains the basic output structure but omits how parameters like 'by', 'period', and filters interact. The ambiguity between 'every stop' and the 'by' granularity leaves some gaps.

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?

All 7 parameters have schema descriptions (100% coverage), so the schema does the heavy lifting. The description adds no parameter-specific information beyond the general 'over a period' phrase.

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 uses a specific verb ('list'), names the resource ('stays'), and specifies the scope ('over a period') and content ('every stop with start, end and duration, the trip it belongs to, and the place'). It also differentiates from siblings by explicitly mentioning reconstruction of a day/week/trip, which sibling tools like 'day' or 'trip' likely serve.

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?

It provides clear context: 'Use it to reconstruct a day, a week or a trip in order.' This tells when to use it, but it does not mention when not to use it or alternative tools explicitly.

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