get_active_promotions

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

With no annotations provided, the description carries the burden of behavioral disclosure. It transparently explains the exact activity filter (is_activated=true and time range), but it does not mention other behaviors such as pagination, sorting, or absence of side effects. As a simple read operation, this is adequate but not rich.

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, concise sentence that defines both the action and the exact criteria for 'active'. It is front-loaded with the main purpose and contains no redundancy or 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?

This is a simple zero-parameter read operation with no output schema. The description provides the necessary filter context to understand what the tool returns. However, it could slightly benefit from mentioning its read-only nature or how it differs from list_promotions, though such omissions are not severe given the simplicity.

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 input schema is empty (0 parameters), and the description correctly focuses on the tool's behavior rather than parameter details. Since there are no parameters, the baseline is 4; the description adds value by explaining the implicit filtering semantics.

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 states the tool's function: 'Get all currently active promotions' with explicit filtering criteria (is_activated=true and within start_time/end_time range). This is a specific verb+resource combination, but it does not explicitly distinguish itself from sibling tools like list_promotions or search_promotions, which may also return promotions.

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?

The description implies when to use this tool: when you need only currently active promotions. However, it does not explicitly state when not to use it or mention alternative tools for broader queries or more complex filtering, leaving some ambiguity.

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