search_promotions

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 mentions filters but omits important behavioral details such as whether it is read-only, what the return format is, and whether pagination is supported. Additionally, the description references a 'date range' filter that is not present in the input schema, which could mislead users.

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, but it includes an inaccurate reference to a date range filter. While concise, the misleading content reduces its effectiveness, earning it a middle score.

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?

The tool has 6 parameters and no output schema, so the description should clarify what the tool returns and any pagination behavior. It does not. It also fails to mention the is_activated filter and includes a non-existent date range filter, making the context incomplete and somewhat confusing.

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 covers 100% of parameters with descriptions, so the baseline is 3, but the description adds little value beyond repeating schema info. It introduces a 'date range' filter that does not exist in the schema, which is misleading. It also omits the is_activated, page, and limit parameters from its summary.

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 purpose: 'Search/filter promotions with advanced filters'. It specifies the resource (promotions) and the action (search/filter). However, it does not explicitly differentiate from sibling tools like list_promotions, but the mention of 'advanced filters' implies a more specific capability.

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 the tool (when filtering promotions by various criteria) but does not provide explicit guidance on when to use it instead of alternatives like list_promotions or get_active_promotions. No exclusions or alternatives are mentioned.

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