create_frame

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

The description only states 'Create a new frame', which is inferred as a mutation. Annotations already indicate readOnlyHint=false and destructiveHint=true, but the description does not clarify what makes it destructive (e.g., overwriting existing nodes) or any side effects beyond creation.

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 a single sentence, efficiently conveying the core purpose without unnecessary words. It is front-loaded and easy to parse, though it could benefit from additional context without losing conciseness.

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?

With 19 optional parameters and no output schema, the description is too sparse. It fails to mention defaults, the auto-layout capabilities implied by parameters, or important behaviors like what happens when parentId is omitted. A more comprehensive description is needed given the tool's complexity.

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% with parameter descriptions, so baseline is 3. The description adds no extra parameter semantics beyond what the schema provides, so no improvement is warranted.

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 creates a 'frame', a specific resource type, and specifies placement ('on the current page or inside a parent node'). This distinguishes it from sibling creation tools like create_rectangle or create_ellipse.

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 no guidance on when to use create_frame versus alternatives like create_section or create_component. It does not mention when not to use it or suggest other tools for different container needs.

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