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

The description discloses two behavioral traits: authentication is required and results are scoped to the caller. Without annotations, this is useful but not comprehensive; no mention of error behavior, pagination, or sorting.

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 two short sentences, directly stating purpose and scope, with no filler.

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 simple list tool with one optional parameter and no output schema, the description covers the core purpose and auth requirement, but it omits the meaning of the status parameter and any response structure details, leaving notable gaps.

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 input schema has a single 'status' parameter with enum values but no descriptions (0% coverage). The description does not explain the status parameter or its filtering effect, leaving the agent to infer from the enum values alone.

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 'List campaigns' uses a specific verb ('List') and resource ('campaigns'), and adds scope with 'the caller's campaigns,' distinguishing it from sibling tools like listActions and listSubmissions.

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 clear context that authentication is required and the tool returns only the caller's campaigns, implying use for self-owned data. However, it does not explicitly contrast with sibling tools like getCampaignStats or createCampaign.

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