set_page_hidden

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

The description goes beyond the sparse annotations by explaining that the tool affects page visibility on the wedding website, with a concrete timing example. Since destructiveHint=false is the only annotation, the description usefully communicates that this is a non-destructive visibility toggle rather than a page deletion or content edit.

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 description is a single sentence that front-loads the core action-verb and resource, then adds a useful example. Every word contributes meaning, with no repetition or filler.

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?

This is a simple two-parameter toggle operation with a fully described input schema and a clear purpose. The description handles the use case and object, while the schema handles the parameters; nothing essential is missing for an agent to invoke the tool correctly.

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%, so both page_id and hidden are already documented with clear meaning. The tool description adds no additional parameter detail beyond what the schema provides, which lands at the baseline score of 3.

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 uses a specific verb-resource pair: 'Show or hide a page on the wedding website'. It also gives a concrete example involving the RSVP page, which makes the purpose immediately understandable and distinct from sibling 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?

The example 'hide the RSVP page until invites go out' gives a clear real-world context for when to use the tool. It does not explicitly name alternative tools or exclusion conditions, but the operation is distinct enough that an agent can infer when to choose it.

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