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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds context the annotations do not: an authentication requirement, that the summary is scoped to the calling user rather than the workspace, and that outcome evidence may be incomplete. That last caveat is genuinely useful for interpreting the result, though it is terse.

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 compact sentences with the payload description front-loaded and the authentication constraint trailing. Nothing is wasted, though the second sentence is a fragment rather than a well-formed clause.

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 parameters and no output schema, the description carries the return-shape burden and does partially discharge it by naming the reported metrics and flagging incomplete outcome evidence. It is sufficient for a no-arg, read-only aggregate, though a fuller listing of returned fields would be better.

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?

The tool takes zero parameters, so the schema baseline is 4. The description still adds a little value by naming the fields the summary reports, which orients the agent even though there is nothing to invoke.

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 states a concrete resource (outreach) and enumerates what the summary contains: total leads, recorded status counts/ratios, and outcome evidence. It is clear what the tool returns, but it never distinguishes itself from adjacent outreach/analytics siblings such as search_outreach_leads or campaign_pipeline_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 mention of when another tool is preferable, and no conditions or exclusions. 'Requires authentication' is a prerequisite, not usage routing, so an agent gets no help choosing between this and the other outreach/analytics tools.

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