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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the agent understands this is a safe, read-only operation. The description adds that the result includes status and contact counts, which is useful but minimal; no further behavioral traits like pagination are disclosed.

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 a single, front-loaded sentence that conveys action, object, and output details with no redundant words. It is concise and easy to parse.

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?

Given the tool's simplicity (zero parameters, safe read-only operation) and rich annotations, the description adequately covers the expected output ('status and contact counts'). No gaps that would hinder an agent's invocation.

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 accepts no parameters, so the schema trivially covers 100%. Per rubric, a tool with zero parameters receives a baseline of 4. The description doesn't need to explain parameter meaning since none exist.

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 starts with the action 'List' and clearly identifies the resource 'this account's outreach campaigns' with specific output details ('status and contact counts'). It distinguishes from sibling outreach_get_campaign, which likely handles individual campaigns.

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's clear scope ('this account's outreach campaigns') implies it is used to enumerate all campaigns, as opposed to outreach_get_campaign for a single one. It lacks explicit when-not-to-use language, but the context is clear enough for an agent.

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