Discounts: campaign statistics

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

Declares read-only, no sends, no charges, and lists return fields. Annotations already indicate safety; description reinforces and adds detail.

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?

Short, front-loaded, no redundancy. Every sentence adds value: purpose, read-only note, return content, usage guidance.

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?

Describes return fields despite no output schema, provides usage context, and distinguishes siblings. Complete for a stats tool.

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?

Schema covers both parameters with descriptions (100% coverage). Description does not add parameter-specific detail beyond stating the period, but baseline is adequate.

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 returns statistics for already-sent discount campaigns over a period, and distinguishes from sibling tools for eligibility checks and tariff info.

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?

Explicitly says to use for analyzing results and provides alternatives for eligibility checks (msg_discounts_open_api_available) and remaining balance (msg_discounts_open_api_tariff_info).

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