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 safety is covered. The description adds genuine value not present in structured fields by disclosing the computed payload (counts, deal totals, message counts, 30-day series) for a tool with no output schema. It omits account scoping and whether the 30-day window is configurable or relative to now.

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?

Two short sentences, front-loaded with the 'KPI summary' label so the agent sees the tool's nature immediately. The telegraphic, comma-spliced style and the unspecified '30-day series' cost a point but nothing is padded.

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 one-parameter, read-only tool with rich annotations and no output schema, the description does the main remaining job: telling the agent what numbers come back. Gaps are minor but real—what the 30-day series measures, and whether results are scoped to the whole account or a workspace/user.

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%, so the single `pipeline` parameter is already documented as 'Per-stage open deals instead.'. The description adds only a mild clarification that per-stage results include both count and value. That is a small increment over the schema, consistent with the baseline 3 for full schema coverage.

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 names the resource (a KPI dashboard summary) and enumerates the exact metrics returned: contact count, open/won deals with totals, messages sent/received, and a 30-day series. That is specific enough to separate it from the *_list siblings, which return records rather than aggregates. It stops short of explicitly contrasting itself with a sibling such as deals_list.

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 call this versus the many list tools (contacts_list, deals_list, sms_list) that could supply the same underlying data in raw form. The only conditional guidance is the 'pipeline: true' note, which describes a mode switch rather than tool selection. An agent must infer from 'summary' that this is the overview/aggregation entry point.

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