Publish Multiple

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

Annotations already declare idempotentHint, destructiveHint, and openWorldHint, so the safety/mutation profile is covered. The description adds genuinely non-obvious behavior beyond that: held pages and fork copies are never published and surface in 'skipped' as {id, reason}, and publish_all_drafts ignores fork copies entirely. These edge cases would be invisible from the schema alone.

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?

Front-loaded with the purpose and the routing directive, then compact examples, then the skip/return semantics. Every sentence carries distinct information and nothing is redundant with the schema.

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?

No output schema exists, and the description compensates by naming the return payload (published IDs, skipped items, failures). Combined with the mutual-exclusivity note and skip rules, an agent has everything needed to call and interpret the result.

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 coverage is 100%, so the baseline is 3, but the description earns above baseline: it illustrates the shape of 'ids' ({"ids": ["abc123", "def456"]}) and clarifies that publish_all_drafts silently ignores fork copies, which the schema property description does not say.

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+resource (bulk publish of content items) and immediately distinguishes itself from the sibling publish_content by routing the agent away from looping. An agent can identify the tool without opening the schema.

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?

Explicitly names the alternative (publish_content) and the condition that selects this tool ('instead of calling publish_content in a loop'). The examples further demonstrate the two invocation modes, so the when-to-use decision is fully inferred.

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