eds_preview_and_publish

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

No annotations provided, and description only mentions atomic operation. Missing details on error handling, prerequisites (e.g., page must exist in draft), permissions, or side effects (e.g., cache invalidation).

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 brief sentences with no redundancy, front-loading the key action and use case.

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 tool combining two operations without output schema, description lacks information on return value, success/failure indication, and preconditions. Incomplete for an AI to use reliably.

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% with parameter description 'Page path to preview and publish (e.g., /about)'. Tool description adds context that path is for a page, but no additional semantic details beyond schema.

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?

Description clearly states the tool previews and publishes a page atomically, and distinguishes from siblings like eds_preview_page and eds_publish_page by combining both operations into one.

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?

The description says 'the most common EDS workflow,' implying primary use case, but does not explicitly state when to avoid this tool or use alternatives like eds_preview_page or eds_publish_page individually.

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