set_document_preferences

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

No annotations are provided, and the description simply states 'Set document preferences' without disclosing behavioral traits such as destructiveness, reversibility, side effects, or required permissions. This is a significant gap.

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 (two words) but lacks structure. It does not convey enough information for a tool with a nested object parameter and an enum, making it under-specified.

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 absence of an output schema and the presence of a nested object parameter, the description is incomplete. An agent would lack understanding of valid preference values and the tool's behavior, requiring additional inference.

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%, meaning the input schema already documents both parameters. The description adds no additional meaning beyond the schema; it does not explain the relationship between preferenceType and preferences or the expected format of the preferences object. Baseline 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?

The description 'Set document preferences' clearly states the action (Set) and the resource (document preferences). It distinguishes the tool from siblings like get_document_preferences and other set_* tools, though it does not specify the scope of 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?

The description provides no guidance on when to use this tool versus siblings like set_document_grid_settings or set_document_layout_preferences. An agent would have no contextual advice on selecting this tool.

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