weekend_promotions

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

With no annotations, the description must carry the full behavioral burden, and it does not. It implies a read operation but never confirms read-only semantics, auth requirements, whether the weekend window is computed server-side, or pagination behavior; only the phrase 'optionally with their products priced' hints at response shape, and the output schema covers returns anyway.

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?

A single tight sentence with the resource front-loaded and no filler. The trailing clause 'with their products priced' is slightly awkward but does the work of flagging optionality.

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?

An output schema exists and there is only one optional boolean, so the bar is low and the description is roughly proportionate. Still, for a tool whose whole value proposition is the weekend scope, it says nothing about timezone, weekend boundaries, or whether an empty result is possible.

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?

One parameter at 0% schema description coverage, so the schema alone does not explain 'with_products'. The description does map to it via 'optionally with their products priced', adding real meaning beyond the boolean's name, but 'priced' is ambiguous — it is unclear whether the flag also controls price inclusion or merely product data.

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?

States a specific resource with a temporal scope: 'This weekend's promotions.' An agent can tell it fetches a time-bounded promotion set, though it never contrasts itself with the sibling tools 'promotions' or 'promotion_details', leaving the boundary between them implicit.

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 when-to-use guidance, no mention of the closely related 'promotions' and 'promotion_details' siblings, and no stated prerequisites. The only steer is the optional products flag, which conveys default behavior rather than selection criteria.

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