youfiliate_get_aggregate_stats

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description reinforces non-modification and adds return field details. However, it does not disclose additional behaviors like rate limits or data freshness beyond what annotations already convey.

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 two sentences with no superfluous words: first sentence states purpose, second sentence lists return fields and safety guarantee. Efficient and front-loaded.

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?

Given the presence of an output schema (implied by 'Has output schema: true') and clear parameter schema, the description adequately covers purpose, return fields, and safety. It lacks explicit contrast with per-link stats but is otherwise complete for a simple aggregate query 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?

The input schema provides full descriptions for both parameters ('period' and 'response_format'), so schema coverage is high. The description adds 'for the specified period' but does not detail enum values or format options. Baseline 3 is appropriate as the schema carries the semantic load.

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 it retrieves aggregate click analytics across all smart links, specifying return fields (total clicks, top countries, devices, referrers) and scope (entire account). It is distinguishable from the sibling tool `youfiliate_get_smart_link_stats` by the word 'aggregate', but does not explicitly name the alternative.

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 notes the tool is read-only ('Does NOT modify any data'), but does not provide explicit guidance on when to use this tool versus per-link stats or other alternatives. The usage context is implied by the word 'aggregate', but no when-not or alternative names are given.

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