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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered. The description adds domain context about what the campaign holds but says nothing about scoping, caching, or auth beyond the workspace parameter. With annotations carrying the behavioral burden, this is adequate but not rich.

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 front-loads the purpose ('what this site is currently saying and to whom') and then lists the concrete fields, ending with the actionable read-before-write cue. It is efficient, though the colon-list is somewhat packed.

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?

For a one-parameter read tool with no output schema, the description does the job of enumerating what comes back (page, pitch, drafts per run, quiet hours, send days) and how to use it. Nothing critical for correct invocation is missing, though return shape details are absent.

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?

Only one parameter exists and schema description coverage is 100%; the schema itself explains workspaceId and points to get_status for listing. The description adds no parameter guidance, which is acceptable given the schema does the work, 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?

The description enumerates the concrete contents of the campaign (linked page, pitch, drafts per run, quiet hours, sending days), which makes clear this is a read of the site's campaign configuration. It does not name a sibling tool it differs from, though 'read this before changing anything' implicitly positions it against the mutation tools like apply_campaign_change.

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?

'Read this before changing anything' gives a clear read-before-write usage pattern that fits alongside set_run_settings, set_link_target, and apply_campaign_change. It stops short of naming those alternatives or stating exclusions, so it is strong context rather than a full routing rule.

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