set_page_display

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

With no annotations provided, the description carries the transparency burden. It clearly explains the meaning of each value (e.g., HiddenInViewMode hides the page from viewers) and the constraint that at least one setting must be provided. It does not detail side effects or permissions, but for a simple setter, the described behavior is sufficient.

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 compact sentence that front-loads the action and resource, uses parentheses for enum lists, and includes the 'set at least one' constraint without waste. Every phrase earns its place.

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?

Given the tool's simplicity and lack of output schema, the description covers the essential behavioral aspects: what can be set, allowed values, and the required constraint. It does not discuss reportSessionId or differentiate from closely related siblings, but overall it provides sufficient context for correct invocation.

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 75%, with descriptions for page, visibility, and displayOption. The description adds context by explaining the visibility values and reiterating the display option enums. However, it does not explain reportSessionId, which is a required parameter lacking schema description, leaving a meaningful gap.

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 clearly states the tool sets a page's display option and/or visibility, enumerating exact allowed values for each. It distinguishes itself from the sibling set_page_visibility by covering both display option and visibility, and by noting both are optional but at least one must be set.

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 description implies usage: use when you need to set display option, visibility, or both. It does not explicitly name alternatives like set_page_visibility for visibility-only cases, leaving some ambiguity about tool selection among the many sibling set_* tools.

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