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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the endpoint path and the shape of returned data (schedule/template/status/reporting), but says nothing about ordering, pagination limits beyond the schema, or how large the result set can get.

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 the primary purpose front-loaded. The trailing raw endpoint path is low-value filler for an agent that already has a typed schema, but it costs only a few words.

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?

With no output schema, the description does the minimum needed by enumerating the returned facets, and pagination is fully covered by the schema's offset/next_offset text. What's missing is whether results are ordered and whether archived or draft campaigns are included.

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% – name, limit and offset are each documented in the schema, including the next_offset continuation hint. The description adds nothing on parameters, 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?

States a clear verb+resource ("List message campaigns") and names the field content returned (schedule, template, status, reporting). The list-vs-get distinction from sibling sakari_get_campaign is implicit in the verb but never explicitly stated.

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?

There is no guidance on when to use this versus sakari_get_campaign for a single campaign, or versus sakari_list_messages when campaign data is really what's needed. The only usage hint is the embedded endpoint path, which is not guidance an agent can act on.

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