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

Annotations already declare readOnlyHint=true, so the safe-read profile is covered by structured data. The description adds that results are aggregated and dimension-grouped and cites the underlying endpoint, but says nothing about result limits, pagination, or how defaults (e.g. event=clicks, a default interval) are applied.

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?

Three compact sentences with zero filler, and the core capability and grouping model are front-loaded before the endpoint reference. Nothing could be cut without losing information.

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?

All parameters are optional and fully documented in the schema, so invocation risk is low, and the description conveys the grouped/aggregated return shape despite there being no output schema. It could still say more about the response structure for the various groupBy values, but coverage is solid for a read-only reporting 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 description coverage is 100%, so all ten parameters are already self-documented, and the description's mention of dimensions and event types largely mirrors the schema's groupBy and event enums. It adds no syntax, format, or interaction detail beyond the schema, so the baseline 3 applies.

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 and resource ('Get aggregated click, lead and sale analytics') plus the grouping model ('grouped by a dimension such as country, device, referer or top links'), which is more than a restatement of the name. It does not, however, distinguish itself from the sibling dub_get_partner_analytics, leaving that differentiation to inference.

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 main reporting read' implies this is the default analytics entry point, but no explicit when-to-use or when-not-to-use guidance is given. The agent must infer that dub_get_partner_analytics covers the partner-side case; the description never names or excludes it.

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