Active offers

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds the scoping detail 'currently active' but omits other important traits such as read-only nature, return format, pagination, or permission requirements. This is minimal disclosure 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?

The description is a single, focused sentence with minimal word count. It front-loads the key information ('Currently active special offers/packages') and contains no filler or redundant phrases.

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 one-parameter getter, the description conveys the core purpose and scope. However, the absence of annotations and output schema means the agent lacks information about return format, pagination, or access restrictions, leaving noticeable gaps for a complete understanding.

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 description adds no parameter-level details beyond the schema, but the schema coverage is 100% with a clear explanation and example (GOLDENSAND) plus a helpful pointer to list_properties. Per the baseline for high schema coverage, a score of 3 is appropriate.

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 clearly identifies the resource as 'currently active special offers/packages for a property', which distinguishes it from sibling tools like get_rates or get_availability. However, it is phrased as a noun fragment rather than a verb phrase ('Get active offers'), slightly reducing actionability.

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 explicit guidance is given on when to use get_offers versus alternatives such as get_rates or get_best_rate. The only contextual hint is 'for a property', which is already evident from the schema. There are no mentions of when-not-to-use or alternative tool references.

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