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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds the useful detail that each entry carries its schedule and an active flag, but says nothing about pagination limits, total counts, or result ordering — the remaining behavioral gap for a list tool.

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?

One short clause, no waste, front-loaded with the resource. However it is a sentence fragment rather than a complete statement, and its brevity comes at the cost of the 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?

The tool is simple — one optional param, read-only, annotations cover safety, schema covers paging input. The description usefully notes the returned fields in the absence of an output schema, but leaves the pagination contract (page size, termination) undocumented, which matters for a list endpoint.

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?

There is a single optional 'page' parameter with 100% schema description coverage including default and minimum, so the schema does the work. The description adds nothing about paging (page size, how to detect the last page), so 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?

The description names the resource (banner campaigns) and the key attributes returned (schedule, active status), but is a noun phrase rather than a verb+resource statement — no 'list' or 'retrieve'. It is not confused with delete_campaign/update_campaign/pause_campaign, but the action itself is only inferable from the name.

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?

No guidance on when to use this versus siblings, no mention of pagination behavior or how to retrieve further pages. The agent must infer usage entirely from the name and schema.

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