create_section

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

Annotations already indicate the tool is not read-only and not destructive. The description adds context about nesting constraints and that the tool creates a new node. It does not discuss permissions or side effects, but the creation operation is straightforward and the return value is specified.

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 pack the definition, placement rules, alternative tool, and return value with zero waste. Front-loaded with the core purpose. Every sentence 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?

Considering the 6 parameters, no output schema, and annotations covering safety, the description explains what a section is, where it can go, and the return format. It could mention that sections are non-visual containers, but the schema and context suffice. The description is complete enough for an agent to use the tool correctly.

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 coverage is 100%, so baseline is 3. The description adds meaning by clarifying the parentId parameter can be a page or another section, which goes beyond the schema description. It does not describe each parameter individually, but the schema already does that adequately.

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?

Description clearly states the tool creates a 'section' as a canvas-level container for grouping and labelling, and distinguishes it from frames by explicitly mentioning create_frame as an alternative. The verb 'Create' combined with the specific resource 'section' and the caveat about not being inside a frame makes the purpose unambiguous.

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?

Description explicitly states when to use (grouping/labelling regions) and when not to (use create_frame for UI containers/auto-layout), and mentions where sections can be placed (page or nested inside another section but not inside a frame). This provides clear guidance on appropriate contexts and alternatives.

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