set_master_page

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

The description only states the operation and labels the parameters; it does not say what 'front' or 'duplicate' flags do behaviorally, what side effects occur, or whether valid values for type and apply_to are limited. With no annotations, this minimal behavior disclosure is a real gap, though nothing in the description contradicts the absence of annotations.

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: a one-line purpose followed by a short Args list. It is scannable and contains no filler, though the terseness limits how much semantic value each line provides.

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 5-parameter HWP document operation with no annotations and no schema descriptions, this is under-specified: the core type parameter is unexplained and apply_to/front/duplicate behaviors are only hinted. An agent could set defaults but cannot know valid values or consequences, even though an output schema exists for return values.

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?

The Args list adds some meaning over the raw schema: doc_id is tied to open_document, apply_to is explained as '0=current section', and front/duplicate are identified as flags. However, type is only restated as 'Master page type' and no valid values or flag semantics are given, so the description only partially compensates for 0% schema coverage.

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 opening sentence 'Set master page settings for the section' names a specific action and target resource, so an agent knows what operation is intended. It does not contrast with nearby page/section tools such as set_page_style or set_section_definition, so sibling differentiation is absent.

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 when-to-use guidance is provided beyond the task statement. There are no exclusions, prerequisites, or references to alternatives in the sibling set, leaving an agent to guess whether set_master_page is the right tool for a given page/section modification.

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