create_text

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

The description highlights that font weight is auto-resolved (e.g., 'bold' → 'Bold'), which adds behavioral context beyond the schema. However, other behaviors (e.g., default values, node creation behavior) are not disclosed, and no annotations are provided to compensate.

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 extremely concise with two sentences. Each sentence adds value: the first states the purpose, the second provides a key behavioral detail. No wasted 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?

Given the tool has 13 parameters, no output schema, and no annotations, the description is too minimal. It does not explain what the tool returns (e.g., node ID), how parentId affects placement, or any other side effects. Completeness is lacking.

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 adds a specific semantic detail for fontWeight (auto-resolution), which provides marginal additional value but does not significantly enhance understanding of other parameters.

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 text' with a specific verb and resource. However, it does not distinguish this tool from related tools like 'set_text_content' or 'style_text_range', which might cause confusion for an AI agent.

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 versus alternatives (e.g., when to create text vs. modify existing text). No prerequisites or context for usage are provided.

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