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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful context beyond that: page size (10 per page), the underlying endpoint (GET /lists), and the returned fields.

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?

Three short sentences, zero waste, front-loaded with the resource and payload fields before the pagination detail. Every clause earns its place.

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?

No output schema exists, but the description lists the return fields and explains pagination, which is enough to call the tool correctly. A minor gap is that it doesn't say whether 'active' excludes archived campaigns, but overall the definition is sufficient.

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 coverage is 100%, so the single page parameter is already documented, including the next_page hint. The description meaningfully supplements this with '10 per page,' which tells an agent how pagination behaves.

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 (List) plus resource (ReferralHero campaigns/lists) and it enumerates the returned fields (uuid, name, subscriber count, creation time). It is clearly distinguishable from siblings like create_campaign or list_subscribers.

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?

States that 'the uuid is needed by every other tool,' which tells an agent this is the natural entry point for dependent workflows. It doesn't explicitly name alternatives or exclusions, but no sibling performs the same listing function.

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