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

No annotations are provided, so the description carries the full behavioral burden. It implies a read, but omits whether retrieval triggers a sync, whether the api_key is required for authorization, rate limits, or default behavior when dates are omitted.

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 sentence, front-loaded with the verb and resource, with no padding. The metric list earns its place because no output schema exists to describe the return fields.

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?

Enumerating return fields compensates for the absent output schema, and safety is not a concern for a read tool. However, with zero required parameters the description never explains default date behavior or auth expectations, leaving gaps an agent must guess at.

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%, with all three parameters (api_key, start_date, end_date) documented in-schema, so the baseline is 3. The description adds no extra parameter meaning such as date format requirements, defaults, or the effect of omitting a range.

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 (Retrieve) and resource (aggregated performance analytics) and enumerates the returned metrics, so the tool's function is unambiguous. It does not differentiate itself from siblings such as reeling_sync_metrics or reeling_get_post_status, which an agent could plausibly confuse it with.

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 guidance on when to use this tool versus alternatives. Nothing says whether metrics must first be refreshed via reeling_sync_metrics, or when to prefer this aggregate view over reeling_get_post_status for individual posts.

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