set_document_preferences

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

No annotations are provided, and the description does not disclose any behavioral traits. It does not mention whether the tool is destructive, requires open documents, or validates input. The description fails to provide essential behavioral context.

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 extremely short (one sentence) but lacks necessary detail. It is under-specified rather than concise. Every sentence should provide value, but this sentence is too generic to be helpful.

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 presence of nested objects, an enum parameter, and no output schema or annotations, the description is severely incomplete. It does not explain return values, side effects, prerequisites (e.g., document open state), or how to use the preferences object structure.

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% (both parameters are described in the schema). The description adds no additional meaning beyond the schema, but per the evaluation criteria, the baseline is 3 when coverage is high. The description neither contradicts nor enriches the parameter information.

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' provides a verb and resource, indicating the tool sets preferences for a document. However, it is vague and does not distinguish this tool from sibling tools like set_document_grid_settings or set_document_layout_preferences, which also set specific preferences. The purpose is clear but lacks specificity.

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 offers no guidance on when to use this tool versus alternatives. Given the many sibling tools for setting specific preferences (e.g., set_document_grid_settings), the description should clarify whether this tool is for general preference setting or only for types not covered by other tools. No usage context is provided.

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