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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that the payload spans several data classes (counts, monitor state, keywords, profiles), but says nothing about aggregation window, cost, or pagination.

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 resource and the dimensions of the overview come first and nothing is redundant.

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?

With no output schema and zero parameter documentation, the description should carry the load but does not: it omits scoping parameters (date range, site vs project), return shape, and when the tool is preferred over the many sibling readers.

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 none of the four parameters (projectId, siteId, from, to) appear in the description. The existence of a from/to date range is a meaningful semantic the agent only discovers by opening the schema, so the description fails to 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?

States a specific verb ('Read') and resource ('lead counts') and enumerates what the overview covers: tier/stage counts, monitor state, keywords, customer profiles. An agent knows this is an aggregate overview rather than a raw list, but nothing explicitly distinguishes it from siblings like list_leads or get_prospecting_summary.

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?

No guidance on when to call this versus list_leads, get_lead, or get_prospecting_summary, and no stated prerequisites (a projectId and siteId are required but not explained). Usage must be inferred entirely from the word 'overview'.

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