document_settings

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

The only annotation is destructiveHint=true, and the description does add real behavioral context beyond it: updates require the current document revision, implying optimistic concurrency. It does not disclose permission needs, what read mode returns, or what happens to settings fields not supplied.

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?

Two sentences, zero filler, and the read/write nature is front-loaded before the write prerequisite. Every clause earns its place.

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?

An output schema exists so return values need not be explained. Yet for a tool that both reads and mutates with destructiveHint=true, 0% schema coverage, and a nested settings object, the description omits auth requirements and merge/replace semantics for supplied settings.

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 0% across four parameters, so the description carries the burden. It partially compensates by naming the settings domains (page, desk, border) and explaining expectedRevision as 'the current document revision', but says nothing about path or workspaceId semantics.

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?

States a concrete verb pair and resource: reads/updates Inkscape page, desk and border display settings. This distinguishes it from neighbors like guides_grids_manage and document_page_adjust, though the read/write dual nature and 'typed' remain slightly vague.

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 prerequisite for writes is given ('Updates require the current document revision'), which is useful. However, there is no guidance on when to choose this over sibling tools such as document_page_adjust or guides_grids_manage, and no when-not conditions.

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