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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description's '[read]' merely restates that, but 'across the merchant's websites' does add a genuine trait: the report aggregates across all merchant websites rather than one. It still says nothing about result shape, pagination, or time-range behavior.

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?

A single front-loaded sentence with zero waste, and the read marker leads. Its brevity borders on under-specification rather than padding, but nothing is redundant.

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?

For a parameterized analytics report with no output schema and an undocumented enum-like parameter, the definition is not complete enough: an agent cannot tell what the report returns, what time window it covers, or what seliee_analytic_type accepts.

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 0% and the single parameter, seliee_analytic_type (default 'VIEW'), is completely unexplained in both schema and description. The description does not compensate at all, leaving the agent guessing what values are valid or what the default does.

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?

Specific verb+resource: it fetches a UTM sources report scoped to the merchant's websites, which is concrete enough for an agent to know what data it returns. However, it does not distinguish itself from the many sibling report tools (get_articles_report, get_social_report, get_website_report, get_metric_report), so an agent must infer the difference from the name alone.

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?

There is no statement of when to use this report versus another analytics report, no mention of required context (date range, website scope), and no alternatives named despite a dense set of report siblings. The only guidance is implicit in the word 'report'.

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