set_page_hidden

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

Annotations only indicate nondestructive behavior. Description clarifies the effect (toggle visibility) but lacks details on side effects, reversibility, or permissions. Adequate for a simple toggle, but could add more context.

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?

Single sentence, front-loaded with action and resource, with a clarifying example. No wasted words.

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?

Tool is simple (2 params, no output schema). Description is sufficient for basic usage and covers the core functionality. Minor gap: no mention of what happens to page content or user experience, but not critical.

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 covers both parameters with description; schema description coverage is 100%. Description does not add new semantic meaning beyond what the schema provides, so baseline score 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?

Description clearly states the verb (show/hide), resource (page), and domain (wedding website). Includes a concrete example (hiding RSVP page) that distinguishes it from sibling page tools like update_page or reorder_pages.

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?

Provides an explicit use case ('hide the RSVP page until invites go out') implying appropriate contexts. Does not explicitly state when not to use or list alternatives, but the example suffices for understanding when to apply.

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