create_text

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

Annotations already indicate a write operation. The description adds that the default font is loaded automatically and the node is appended to a parent or current page, providing context beyond the safety profile. However, potential error cases (e.g., font loading failure) are not disclosed.

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 with clear structure: action, parameters, optional behavior, return value. No unnecessary words.

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?

The description covers the core function and return value but lacks details on coordinate system, units, default values for x, y, fontSize, and error handling. Given the tool's modest complexity, it is adequate but has clear gaps.

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 only 40% (2 of 5 parameters have descriptions). The description adds that x, y, fontSize are for 'sized/positioned' but does not provide ranges or defaults. It clarifies that characters are required and default font is used, adding some value but not fully compensating for the low schema coverage.

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 it creates a TEXT node with given characters, default font auto-loaded, optional sizing/positioning, and appending to a parent or current page. This distinguishes it from siblings like create_rectangle or set_text.

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 implies use for creating a new text node but does not explicitly state when to use alternatives like set_text or set_text_properties. No usage conditions or exclusions are given.

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