Create Text

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

The description only states the action 'create', but does not disclose behavioral traits such as error handling (e.g., invalid layer/color, zero height), truncation of long text, or the effect of default values. Annotations indicate readOnlyHint=false, so mutation is expected, but no additional context is provided.

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 that directly states the tool's purpose with no extraneous words. It is front-loaded and efficient.

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 is fairly complete given the simplicity of the tool and the presence of a full input schema and output schema. However, it lacks usage context compared to its sibling mtext tool, which slightly diminishes completeness.

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 100%, so the schema already documents all parameters. The description does not add any new meaning beyond naming the key parameters (text, x, y). Baseline score of 3 is appropriate.

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 action 'Create' and the resource 'single-line text entity (DTEXT/TEXT)', which is specific and distinguishes it from sibling tools like entity_create_mtext for multi-line 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?

No guidance is given on when to use this tool versus alternatives (e.g., entity_create_mtext for multi-line, leader_create_mleader, or block attributes). The agent must infer usage from the type name.

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