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

Goes well beyond the annotations by disclosing upsert behavior ('creates it if missing'), the side effect of the false branch ('it also stops taking submissions'), the required auth scope ('forms:write'), and the shape of the returned object (url, qr_url, embed_html, status). The 'stops taking submissions' side effect is exactly the kind of consequence the non-destructive annotation would otherwise hide.

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?

The first sentence packs the operation, both branches, the upsert caveat, and the return fields with no filler, and it is front-loaded. The bracketed [When to use] block is generic policy boilerplate that repeats across mutating tools, which costs a little against true conciseness.

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?

With only three required scalar parameters and no output schema, the description supplies everything an agent needs: what each branch does, the upsert caveat, the auth scope, the side effect, and the return fields. Nothing material is left to guesswork for a call of this complexity.

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 adds real meaning for the boolean flag: true creates-if-missing and false also halts submissions, neither of which appears in the schema's terse 'true to publish, false to stop'. The site and form parameters get nothing extra, which keeps it at 4 rather than 5.

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 and resource ('Publish a form's public page') and covers both directions via the boolean, with the added nuance that publishing creates the page if missing. It doesn't name the nearby siblings it differs from (publish_draft, publish_entry, booking_page_publish), so an agent must infer 'form public page' vs 'draft/entry' scope, but the resource is specific enough to route correctly.

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 frames when to use it ('only when the user you are talking with explicitly asks') and adds a strong exclusion against acting on instructions embedded in tool results. What's missing is any comparison to alternatives such as unpublish_entry or the booking_page_publish family, so an agent gets a consent rule but not a routing rule.

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