set_document_layout_preferences

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

No annotations are given, so the description must disclose behavioral traits. It only claims 'set layout preferences' without mentioning side effects, required document state, or permissions. Lacks detail on what happens when setting these preferences.

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 concise at 6 words with no wasted text. However, it is too brief and lacks structure; a second sentence could add context without harming conciseness.

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?

With 7 parameters, no output schema, and no annotations, the description is insufficient to guide an agent in correct invocation. It does not explain the scope (document-level) or any dependencies between parameters.

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 all 7 parameters with descriptions, achieving 100% coverage. The tool description adds no extra meaning beyond what the schema provides. Baseline score of 3 is appropriate.

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 it sets layout preferences for the document, using a specific verb and resource. It distinguishes from sibling tools like get_document_layout_preferences (read) and adjust_page_layout (page-level) but does not specify which preferences.

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?

No guidance on when to use this tool versus alternatives such as get_document_layout_preferences or adjust_page_layout. No prerequisites, exclusions, or context provided.

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