create_section

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

Annotations indicate readOnlyHint=false and destructiveHint=false, so this is a non-destructive write operation. The description adds that sections are grouping containers that can nest, but does not disclose other behavioral traits such as whether creating a section can affect existing nodes, performance implications, or authorization needs.

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 two well-structured sentences with no redundancy. It front-loads the tool's purpose and then explains placement and output, making it easy to scan.

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 tool's complexity (6 parameters, no output schema), the description is incomplete. It explains the return shape but fails to describe all parameters adequately or mention any constraints on section content (e.g., can it contain any node type?). The low schema description coverage further compounds the gap.

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 only 17% (only parentId has a description). The description briefly mentions 'sized / named / positioned' to hint at x, y, width, height, name, but provides no specific semantics like coordinate system or units. For a tool with 6 parameters, this is insufficient to guide an agent on correct usage.

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 verb 'Create' and the resource 'section', explaining it as a 'canvas-level grouping container' and noting it can be 'optionally sized / named / positioned'. This distinguishes it from sibling tools like create_frame or create_rectangle, which create different node types.

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 mentions that sections live on a page or inside another section, providing some context. However, it lacks explicit guidance on when to use this tool versus alternatives (e.g., frames, rectangles) and does not list any exclusions or prerequisites.

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