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

Annotations already declare the safety profile (not read-only, not destructive, closed-world). The description adds real value with 'draft' — the campaign is not live until activated — but omits the critical behavioral distinction that 'auto_publish' mode publishes without review, which an agent needs before calling.

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 front-loaded sentence with no filler. Efficient, though the brevity is arguably over-compression given the tool's complexity rather than a model of crispness.

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 an 11-parameter, 10-required tool with a nested object and no output schema, the description is far too thin. It should at minimum explain the mode enum semantics, the cadence shape, and account targeting.

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% across 11 parameters, including a nested cadence object, so the description carries the full burden and does not meet it. It vaguely gestures at pageUrl ('a page'), scheduling ('scheduled'), and mode ('draft') but explains none of accountIds, cadence fields, maxPostsPerAccount, or autoPublishAccountIds.

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 (create), resource (distribution campaign), and outcome (a draft that turns a page into scheduled social posts). The word 'draft' cleanly separates it from activate/pause/cancel siblings, though no sibling is named explicitly.

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 when-to-use guidance, no prerequisites, and no alternatives. The agent can infer it precedes activate_distribution_campaign from the word 'draft', but nothing states that workflow or when to prefer this over atomize_distribution_page.

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