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

Annotations already establish readOnly, non-destructive, closed-world behavior, so the description's job is to add context — and it does: it discloses that results are 'customer-visible' (a visibility scoping rule) and 'bounded page' (pagination-limited output). It does not describe ordering or what a page boundary means in practice, which keeps it below a 5.

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 sentences, no filler, with the core capability front-loaded before the sibling-differentiation clause. Every clause earns its place and nothing is repeated from the schema or annotations.

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 output schema and annotations relieve the description of explaining return values and safety, and the content scope plus the budget/funding exclusion are covered. What is missing is pagination semantics and parameter meaning for a 3-parameter tool with zero schema description coverage, which leaves a real gap for correct invocation.

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 0%, so the description must carry parameter meaning, and it largely does not. 'For an artist' faintly implies artistId and 'bounded page' faintly implies limit/offset, but defaults (20/0), the 100 maximum, and offset's role in paging are never mentioned — an agent cannot infer paging strategy or bounds from the description alone.

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: 'Read a bounded page of customer-visible campaign management state for an artist,' then enumerates the content ('lifecycle, targeting and optimization settings'). This separates it from dynamoi_list_campaigns and dynamoi_get_campaign, though 'campaign management state' remains an abstract umbrella term that an agent must infer from the enumerated sub-areas.

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?

Provides one explicit negative pointer — 'use campaign detail/settings for budgets and funding review' — which is useful routing. However, there is no positive 'use this when' statement and no guidance distinguishing it from the many other campaign siblings (list_campaigns, get_campaign, get_campaign_readiness, get_meta_campaign_groups), so an agent still has to guess in the common case.

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