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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description contributes nothing beyond that, not even what the KPI set covers or whether results are scoped to a workspace/document set.

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 clauses, one of which is an exact duplicate of the first. The redundancy is pure waste and the useful content (the describe_operation pointer) is buried at the end rather than front-loaded.

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?

No output schema, a nested open-ended query object, and no return-value or filter information anywhere. For an analytics endpoint with a free-form query parameter, the definition leaves an agent unable to construct a correct call without a second tool call.

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 two parameters include an untyped free-form 'query' object with additionalProperties: {}, so the schema explains almost nothing. The description does not compensate at all — no mention of supported filters, date range, or expected query keys; it only defers to describe_operation.

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 only restates the HTTP path 'GET /api/redline-analytics/kpis' twice, adding no verb-and-resource framing beyond the tool name. It never says what a 'KPI' payload contains or how it differs from siblings like get_redline_analytics_summary or get_redline_analytics_risk_dashboard.

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 sole guidance is a pointer: 'describe_operation provides native request schemas.' That is discoverability help, not when-to-use guidance — no condition, no exclusions, no comparison against the four sibling redline-analytics endpoints an agent must choose between.

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