kadam_adv_get_stats

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

Annotations mark readOnlyHint=true, confirming it's safe read-only. The description adds context on report types and human-readable naming conventions, going beyond the annotation without contradiction.

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?

Two sentences, front-loaded with purpose, and each sentence adds value (type selection, naming examples). No fluff.

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?

With 19 parameters and no output schema, the description covers only the core reportType and naming conventions. Missing details on pagination, filtering, sorting, and return format limit completeness for complex queries.

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 coverage is only 21%, so description must compensate. It explains reportType, metrics, groupBy, and notes conversion-specific parameters. However, many parameters (period, dateFrom, page, etc.) lack explanation, leaving gaps for an AI agent.

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 is for 'Unified advertiser statistics' and explains the three report type options (custom, sites, conversions), which distinguishes it from sibling tools that handle CRUD operations.

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 tells when to use each reportType, providing context for selecting the appropriate mode. While it does not explicitly exclude alternatives, the sibling tools are all mutation/creation, making this the only stats tool.

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