get_active_promotions

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

readOnlyHint=true already tells the agent this is a safe read, so the description's main added value is operationalizing 'active' as is_activated=true plus a start/end time window, which prevents a misread of the filter. It says nothing about return volume, ordering, or pagination for what could be a large set.

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 sentence with the resource and the defining filter front-loaded; there is no filler and nothing that could be cut without losing meaning.

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 parameterless read with no output schema and a one-line annotation, the description supplies the one thing that matters: what 'active' means. Missing only secondary details such as result ordering or whether results are capped.

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 tool takes zero parameters, so there is no parameter semantics to convey; the schema is empty and nothing in the description contradicts it. Baseline 4 applies for a no-parameter tool.

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 verb ('Get') and resource ('promotions') and pins down the scope with the parenthetical definition of 'active' (is_activated=true and within start_time/end_time). This implicitly separates it from sibling readers like list_promotions, search_promotions, and get_promotion, though none of those siblings are named.

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 'currently active' predicate implies when to reach for this tool versus an unfiltered listing, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative. Usage must be inferred from the scope qualifier.

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