Create Text

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

Annotations only have openWorldHint, so description should disclose behavioral traits. It doesn't mention side effects (e.g., does it auto-layout?), required permissions, or what happens if parentId is invalid. For a creation tool, this is insufficient.

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?

Single sentence, no redundancy. Efficiently conveys the core function.

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?

Despite having 9 parameters and nested objects, the description is minimal. It doesn't explain the fontColor object structure, return value (output schema exists but not described), or coordinate system. More context needed for a creative tool.

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 description adds little beyond listing parameters. It mentions 'optional font size/weight/color' but those are already in schema. No added context like coordinate system or units.

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 'Create a text node' with content and optional styling. It distinguishes from siblings like 'create_shape' by specifying text. However, it could be more explicit about its role among creation tools.

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 guidance on when to use this tool vs alternatives like 'create_frame' or 'text_set_style'. No prerequisites (e.g., need a parent frame) or exclusions. The description is purely functional.

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