modify_hierarchical_sheet

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

The annotations already indicate destructiveHint=true, and the description merely restates 'modify' without adding behavioral context such as side effects, irreversibility, permissions, or file system impact. It does not disclose anything beyond what the annotations provide.

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 well-structured with a one-sentence summary followed by a concise, line-per-argument list. Every line holds necessary information, making it efficient and 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?

Given the 6-parameter complexity, the presence of an output schema, and annotations, the description sufficiently covers parameter semantics and selection context. It lacks only minor behavioral details like saving or file write effects, which are not required due to annotations and output schema.

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?

With 0% schema description coverage, the description's Args section fully compensates by explaining each parameter's meaning and default behavior (e.g., 'None = keep', 'empty = keep', and source of sheet_uuid). This is critical for correct invocation and adds significant value.

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 the tool modifies properties of an existing hierarchical sheet block, using a specific verb and resource. This distinguishes it from sibling tools like add_hierarchical_sheet, remove_hierarchical_sheet, and move_hierarchical_sheet.

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 clear context by stating it operates on an existing sheet identified by sheet_uuid from list_schematic_sheets. It implies when to use it (modify existing) but does not explicitly name alternatives like add or remove, so it lacks explicit exclusion guidance.

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