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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description does add real behavior beyond them: results are scoped to the calling user and returned most-recently-updated-first. It does not mention that results are silently capped at a default 50 rows, which matters for completeness of a listing.

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 with zero filler; the resource and default ordering are front-loaded and the optional filters follow. Every clause carries information an agent needs.

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 read-only list tool with full schema coverage and no output schema, the definition covers resource, scope, ordering, and filtering adequately. The only real gap is the unstated default row cap and no mention of how to page past it.

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 description coverage is 100%, so all three parameters are already documented in the schema, including the q substring semantics and the status enum. The description only restates that filtering exists, adding no format or matching nuance beyond the schema, so the baseline of 3 applies.

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?

States a specific verb and resource ("List the Phone Bud user's campaigns") plus the scope (current user's own campaigns) and the ordering ("most recently updated first"). It reads clearly against the sibling get_campaign by being a plural, filtered listing, but it never explicitly distinguishes itself from that sibling or from list_contacts/list_agents.

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 phrase "Optionally filter by status or a name/goal substring" implies when the filters are useful, but there is no explicit when-to-use/when-not guidance and no pointer to get_campaign for fetching a single campaign by id. An agent must infer the routing itself.

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