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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is clear. The description adds that results include status and statistics, which is useful beyond annotations, but it does not cover pagination, sorting, result limits, or response shape. Given the annotation coverage, a 3 is appropriate.

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 a single short sentence with no filler, and the key information ('campaigns', 'status and stats') is front-loaded. It is perhaps too terse, but under-specification is better assessed under contextual completeness.

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?

For a zero-parameter read-only list tool, the description gives a minimal sense of return content by mentioning status and stats. However, with no output schema, it should do more to describe what a campaign record contains, whether all campaigns are returned, and whether any pagination or ordering applies.

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 no parameters, so the baseline is 4. The description does not need to explain parameter meaning, and the schema coverage is 100%.

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 name and description together indicate that this returns a collection of the account's outbound campaigns along with status and statistics. However, the description lacks an explicit verb like 'list' and never distinguishes this tool from siblings such as get_campaign or list_campaign_contacts. It is understandable but vague.

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 guidance on when to use this tool versus get_campaign, list_campaign_contacts, or other campaign-related siblings. The only implied context is that it returns a collection, which the agent must infer from the name and the phrase 'Your Outbound campaigns'.

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