Republish a page

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds that the page returns at its existing URL, which is genuinely useful context, but says nothing about permissions, what happens if the page is already published, or whether prior content/settings are preserved.

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 short sentence with the action front-loaded and no filler. Nothing to trim and nothing buried.

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 tool whose annotations already cover the safety profile and which has no output schema, the description covers the essentials. The remaining gap is the undocumented pageId and the undefined behavior when the page is already published.

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?

There is one required parameter (pageId) with 0% schema description coverage, so the description carries the burden of explaining it and does not. 'Page' implicitly maps to pageId, but no format, ID convention, or source of the ID is given.

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 gives a specific verb phrase ('Bring ... back online') plus the resource ('page') and a scope detail ('at its existing URL'), so the action is unambiguous. It does not name siblings such as publish_html or publish_presentation, but 'page' vs 'html' vs 'presentation' is readable from the resource word.

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 condition is implied by 'unpublished page', i.e. use this when a page is currently offline, which implies unpublish_page is the inverse and no other sibling fits. There is no explicit statement of when-not to use it or what alternatives exist.

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