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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds substantive value by disclosing the shape of the result (which fields come back) in the absence of an output schema, plus the endpoint path. It doesn't mention pagination behavior or result ordering, which are typically documented in the schema.

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 compact sentences: resource, filters, endpoint. Front-loaded and free of filler. Slightly terse – the endpoint fragment at the end carries little value for an agent that already knows the tool name.

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, and the description compensates by naming the returned fields; pagination and ranges live in the schema, and safety lives in annotations. Complete enough to call correctly, with only ordering/pagination semantics left implicit.

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%: limit, state, offset and search are all documented with defaults, ranges, enums and even the next_offset guidance. The description only restates the two filter concepts without adding syntax or semantics, so the baseline 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?

Opens with a specific resource ('Campaigns of the account') and enumerates the fields returned (id, name, kind, created/edited, recipient count), so the agent knows exactly what a call yields. It doesn't explicitly contrast with siblings like sarbacane_get_campaign or sarbacane_list_campaign_recipients, which keeps it from a 5.

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?

'Filter by state or a text in the name or subject' implies when the filters are useful, but there is no statement of when to prefer this over sarbacane_get_campaign (single campaign detail) or other list siblings. Usage is inferable rather than stated.

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