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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds context beyond that: it is 'DB-backed and instant,' and it explains what `undecided` means ('the ones nobody has judged yet'), which is genuine semantic disclosure.

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?

It is front-loaded with the primary content (the verdict counts) before layering on booking metrics and scoping. It is dense and slightly run-on, but every clause carries information rather than padding.

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, the description carries the burden of explaining return values, and it does so thoroughly by naming the count categories and booking metrics. All params are optional and the scoping behavior is covered, leaving only minor ambiguity around what 'you can see' precisely means.

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 all three params (sessionId, campaignId, sessionLabel) are already documented in the schema, making 3 the baseline. The description echoes the sessionLabel/campaignId scoping but does not add syntax or format detail beyond the schema, and omits sessionId entirely.

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?

Specific verb-and-resource: it enumerates the exact human verdict counts (won, meetingBooked, interested, notInterested, noOutcome, undecided) and the per-account booking metrics it returns. It also explicitly distinguishes itself from siblings by stating it is 'the only measure of RESULT in the system: every other count says what the automation did.'

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?

It gives clear context for when to reach for this tool ('the only measure of RESULT') and how to narrow it (sessionLabel and/or campaignId), which implicitly contrasts it with activity-count tools like li_outreach_analytics. It stops short of naming those siblings explicitly or stating exclusions.

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