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

Annotations already declare readOnlyHint=true, so the safety profile is covered and the bar is lower. The description usefully discloses the return payload shape (statuses, timestamps, completion_percentage, audience) and the underlying endpoint, but says nothing about pagination traversal, ordering, or result limits beyond what the schema already documents.

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?

A single dense sentence that front-loads the action and resource, then lists the payload contents, followed by the endpoint. No filler and nothing repeated from structured fields.

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 field enumeration in the description is the only documentation of return values and it covers the essentials well. It falls short only on list-operation conventions such as ordering or how many results a default call returns, which the schema partially covers via limit/offset.

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% and all three parameters (limit, offset, status) are already well annotated, so baseline is 3. The description restates the status examples ('draft, scheduled, queued, sent'), adding marginal value but no syntax or edge-case detail 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?

States a specific verb and resource ('List the brand's SMS/MMS campaigns') and enumerates the fields returned, so the agent knows exactly what it fetches. It implicitly contrasts with the singular sibling slicktext_get_campaign via 'List', but never names an alternative, so sibling differentiation is left to inference.

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 when-to-use guidance, no prerequisite (e.g. brand_id source), and no mention of when to prefer slicktext_get_campaign, get_campaign_stats, or the paginated siblings. The description only says what it returns, leaving the selection decision entirely to the agent.

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