get_stay_history

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

With no annotations, the description carries the full burden of behavioral disclosure. 'Read' implies a safe read operation, but no other behavior is disclosed—no mention of pagination, ordering, what a 'stay' consists of, or whether any side effects occur. The description adds minimal transparency beyond the verb.

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 extremely brief, which could be seen as concise, but it is under-specified rather than efficiently sized. It is front-loaded in the sense that the only information is at the start, but there is no structure or additional detail to justify its brevity.

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?

Given the tool's single optional parameter, lack of output schema, and no annotations, the description is wholly inadequate. It does not explain what past stays are, what data is returned, or any ordering or filtering behavior. An agent cannot reliably call this tool based on the description alone.

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 schema coverage is 0% and the description does not mention the 'limit' parameter at all. The description adds no meaning to the parameter, so the agent has no idea how to set or interpret it.

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 states a specific verb ('Read') and resource ('past stays'), but 'stays' is ambiguous and there is no differentiation from the sibling get_reservation, which likely also deals with stay-related data. The purpose is somewhat clear but not precise enough for an agent to distinguish it.

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?

No guidance is provided on when to use this tool versus alternatives like get_reservation. The description gives no context, prerequisites, or exclusions, leaving the agent to infer usage entirely.

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