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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so safety is covered. The description adds non-annotation context: it discloses return structure (summary.platformMetrics holds per-channel metrics) and the single-range-per-call constraint, which materially affects how an agent plans calls.

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?

Four tight sentences, front-loaded with the verb and range scoping, then output structure, then the single-range constraint. No filler, though it leans on an unexplained dot path (summary.platformMetrics).

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 an 8-parameter, nested, output-schema-less tool, the description covers the essential range mechanics and one return field but omits several parameters and any sibling routing. Adequate but leaves clear gaps an agent must fill by trial.

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?

With only 25% schema description coverage, the description carries real burden. It usefully explains timeframe (example "30d"), the startDate/endDate alternative, and workspace_id, but leaves brand_id, includeActivity, includeInsights, and query unexplained in both schema and prose.

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 (Summarize) and resource (workspace analytics) with the scoping dimension (timeframe or startDate/endDate range). Clear on its own, but it never distinguishes itself from close siblings like get_analytics_unified, get_analytics_insights, or get_post_analytics.

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?

It hints at usage by clarifying that one call covers one range and a trend requires comparing two separate ranges, which is genuinely useful context. However, it names no alternative tool and gives no explicit when-to-use/when-not guidance against the several other analytics siblings.

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