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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered structurally. The description adds nothing beyond that — no mention of aggregation granularity, whether results are paginated, or how the date range interacts with lead scope.

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?

The text is short but that brevity comes from under-specification, not economy — it is two near-duplicate fragments separated by a dash. Nothing is front-loaded beyond the redundant name echo.

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?

An output schema exists, so return values need not be explained, but the description still fails to tell the agent what distinguishes this engagement-level analytics endpoint from its many siblings. For a zero-required-param analytics query in a crowded namespace, that leaves the agent without the context needed to select it correctly.

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 five parameters (from/to/skip/limit/workspace_id) documented in the schema. The description adds no meaning beyond that, so the baseline of 3 applies.

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 'Get Lead-level Analytics - Lead-level stats' is a tautology that merely restates the tool name and title. It never says what a 'lead stat' contains (opens, clicks, replies, per-lead aggregates) or how it differs from the many sibling analytics tools such as get_analytics_overall, get_analytics_daily, get_analytics_mailbox_stats, or get_sequence_stats.

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 when-to-use guidance, no exclusions, and no mention of the adjacent analytics siblings an agent must choose between. An agent has no basis from the description for preferring this tool over get_analytics_overall or get_sequence_stats.

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