set_page_hiding

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the operation and that fields is a bitmask, but it does not clarify side effects, whether the setting applies to the current page or all pages, whether it is reversible, or how the bitmask values map to specific elements.

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 compact and well-structured, front-loading the purpose and then listing arguments. It contains no redundant content, though it is arguably too sparse to fully support correct invocation.

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 tool with a bitmask parameter and no schema-level parameter descriptions or enums, the description is incomplete. The output schema does not compensate for missing bitmask semantics, usage context, or behavioral details, so an agent cannot reliably construct a correct call.

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 0%, so the description must compensate. It does add meaning by explaining doc_id as coming from open_document and fields as a bitmask of elements to hide, but it fails to enumerate bitmask values or provide examples, leaving a key parameter under-specified.

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 a specific action and resource: 'Set page element hiding' with examples (header, footer, border). It is more informative than a tautology and conveys the tool's role, though it does not explicitly differentiate itself from related siblings like set_header_footer or set_page_border.

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?

There is no guidance on when to use this tool versus alternatives, and no exclusions or prerequisites beyond the implication that a document must be open. The arg note 'doc_id: Document ID from open_document' hints at context but does not explain when this operation is appropriate.

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