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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered; the description adds the useful disclosure of which fields are returned despite there being no output schema. It stops short of describing result volume, pagination in the description, or ordering, but the safety context is fully carried by annotations.

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?

Two short sentences, response fields front-loaded, followed by the natural next step. No filler and nothing important buried.

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 one-parameter read-only list tool with no output schema, the description is nearly sufficient: it names the returned fields and the follow-up path, with pagination fully handled by the schema. Minor gaps remain around result volume/ordering and how it differs from the campaign-events and summaries siblings.

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 single `page` parameter is 100% documented in the schema, including pagination semantics (sets of 10, keep going until empty), so baseline 3 applies. The description adds nothing about paging or filtering beyond the schema.

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 ("the account's email campaigns") and even the fields returned (uid, name, status, dates), so the agent knows exactly what comes back. It distinguishes itself from detail-fetching siblings by pointing at the campaign uid as the gateway to "details and reports," though it does not name those sibling tools explicitly.

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?

Usage is implied rather than stated: the agent is told to obtain uids and then use them for details/reports, which suggests this is the discovery step preceding get_campaign / get_campaign_summaries. There is no explicit when-to-use, no exclusions, and no mention of the related list_campaign_events tool that an agent might otherwise confuse it with.

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