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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds meaningful behavior beyond annotations by flagging that emails are sensitive and that an account-owner connector with publish permission and write access is required, which is important context for invocation.

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 description is three sentences with no filler. The action and scope are front-loaded, the output contents are summarized compactly, and the permission note earns its place because it is essential for correctly invoking the tool.

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?

The description is complete for a read-only list tool: it covers purpose, scope, included data, use case, and access requirements. An output schema exists, so return values do not need to be described. It slightly falls short of a 5 by not explicitly steering the agent toward or away from sibling analytics tools, but nothing essential is missing.

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 both limit and publication_id are already documented. The description adds context like 'for one publication' but does not provide significant new meaning beyond the schema's parameter descriptions, so the baseline score of 3 is appropriate.

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 opens with a specific verb and resource: 'List visitor leads for one publication.' It enumerates exactly what is included—verified and unverified emails, visit timing, visit count, per-path activity, and recent access sessions—so the agent can distinguish it from related publication tools without opening their schemas.

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?

The description provides a clear use case: 'Use this to follow up without opening the Revdoku dashboard.' It gives contextual guidance but does not explicitly name alternatives or state when not to use this tool, though sibling names such as bucket_publication_analytics are available for the agent to consider.

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