set_document_grid_settings

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

No annotations are provided, so the description must convey behavioral traits. It only says 'Set comprehensive grid settings' without disclosing that it modifies existing settings, whether it overwrites or merges, or any required permissions. The agent knows it is a mutation but lacks details on side effects.

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, concise sentence that captures the tool's purpose without unnecessary words. It is front-loaded with the action and object, making it easy to parse.

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 11 parameters, no output schema, and no annotations, the description is too brief to provide complete context. It does not mention that all parameters are optional, or how the tool interacts with document grid and baseline grid settings. The agent would need to infer usage from the schema alone.

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 all parameters have descriptions in the schema. The description does not add any additional meaning beyond the schema, so baseline 3 is appropriate. It does not clarify relationships between parameters like gridAlignment and the enable/disable booleans.

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 that the tool sets comprehensive grid settings for the document. It distinguishes itself from the sibling 'get_document_grid_settings' by indicating it is a setter, but could be more specific about the grid types (document grid and baseline grid) which are evident in the schema.

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 like other set_* tools. There is no mention of prerequisites, such as requiring an open document, or when not to use it. The agent must infer from the name and schema.

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