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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds no behavioral context beyond that — it does not mention rate limits, freshness/latency of the data, or any constraint not already in the schema — so it neither helps nor contradicts.

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 no filler; the key resource is named immediately. It is appropriately sized, though it could have used the space to route between analytics siblings.

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?

An output schema exists, so return values need not be explained, and the read-only profile is covered by annotations. However, for a tool that sits among a dozen analytics siblings, the absence of any routing guidance leaves a meaningful gap for correct selection.

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 50%; the schema itself documents the 30-day date-range cap and the metric enum, while the description only restates a few metric names already in the enum. It adds no syntax or semantics for filters.source_id or group_by, so it does not compensate for the coverage gap.

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 states a specific verb and resource ('get image analytics data') and names concrete example metrics, so the agent knows this is an image-analytics retrieval tool. It does not, however, differentiate itself from the many analytics siblings (asset_analytics, live_usage_analytics, retrieve_analytics, insights_*, analytics_*), leaving the agent to infer that 'image' is the distinguishing scope.

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 when-to-use guidance, no mention of prerequisites or exclusions, and no routing to any of the numerous analytics alternatives in the sibling list. The agent has to guess why it would pick this tool over retrieve_analytics or asset_analytics.

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