set_option

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose two genuine traits: writes go through Dorico's own commands, and the setoptions message path ignores layout ids (a real caveat about layout_ids not taking effect in some route). It says nothing about permissions, reversibility, persistence across reloads, or what happens on an invalid path, which for a mutation tool with zero annotation coverage is a notable 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 definition is compact and front-loaded, leading with the action and the enumeration source before the kind breakdown. The final parenthetical about the setoptions message ignoring layout ids is terse to the point of being hard to parse, but every sentence carries information.

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?

For a five-parameter mutation tool with no annotations and no output schema, the description covers the essentials: what it writes, where valid paths and values come from, and which params bind to which kind. What is missing is error/confirmation behavior and a clearer statement of the layout_ids caveat, but no output schema means return values need not be described.

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%, so the description must compensate and it does so partially: it names the kind values and maps flow_ids to kNotation and layout_ids to kLayout, which the schema's bare titles do not convey. It gives no syntax or format detail for path and value beyond "from get_options," leaving the two most-used required parameters underspecified.

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 pairs the specific verb "Set" with the specific resource "house-style option" and immediately routes the agent to get_options as the source of valid paths and values, which distinguishes it from the read-side sibling. It also enumerates the three kind values (kEngraving, kNotation, kLayout), so the agent knows the axis of variation without opening 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?

Guidance is implied rather than stated: "paths and values from get_options" tells the agent to call get_options first, and the kind-to-parameter mapping hints at which optional params apply. However there is no explicit when-to-use versus alternatives such as set_property or dialog_set, and no statement of preconditions or failure modes.

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