set_page_hidden

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

Annotations declare destructiveHint=false and openWorldHint=true, so the safety profile is partly covered already. The description confirms the mutation affects the public wedding website (open world), which is useful, but it adds no detail on permissions, whether hiding is reversible, or impact on already-published pages.

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 a concrete example; nothing is wasted and the action is stated first.

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 two-parameter boolean toggle with complete schema coverage and no output schema, the description is largely sufficient. Slightly more context on the effect of hiding a live page would make it fully complete.

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 100%: the boolean 'hidden' and 'page_id' (sourced from list_pages) are fully documented in the schema. The description adds no additional parameter meaning, so the baseline of 3 applies.

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 pair (show/hide) and resource (page on the wedding website), so an agent immediately understands it toggles page visibility. It is distinct from list_pages/reorder_pages, though it doesn't explicitly contrast with update_page, which could plausibly also alter page state.

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 parenthetical example ('hide the RSVP page until invites go out') implies a real use case, giving implied rather than explicit guidance. There is no statement of when to prefer this over update_page or any prerequisite/ordering advice.

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