set_document_preferences

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

With no annotations, the description must disclose behavioral traits. It only states 'set' without indicating whether it overwrites or merges preferences, what the effect is on existing settings, or if it requires an open document. No behavioral context is provided.

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, making it concise but severely under-specified. It lacks front-loading of critical information and does not earn its place with useful content beyond the tool name.

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 complexity of two parameters (one nested object) and no output schema, the description should explain accepted values for preferences based on preferenceType, validation rules, or side effects. It provides none, leaving the agent without sufficient context 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 coverage is 100%, so the schema already defines both parameters (preferenceType enum and preferences object). The description adds no additional meaning beyond what the schema provides, meeting the baseline for complete schema coverage.

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 'Set document preferences' essentially restates the tool name without adding specificity. It does not indicate what types of preferences (e.g., grid, guides, text) or how it differs from more targeted setters like set_document_grid_settings.

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 provides no guidance on when to use this tool versus siblings like set_document_grid_settings or set_document_layout_preferences. It does not mention prerequisites, scope, or exclusion cases.

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