Create MText

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

Annotations already indicate this is not read-only, and the description aligns by saying 'Create', which signals mutation. The description adds the concrete behavioral detail of word-wrap at a specified width, but does not disclose other side effects like whether an entity ID is returned or how defaults behave beyond what the schema already provides.

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?

A single, front-loaded sentence that states the key action, resource type, and distinguishing feature (word-wrap at width). Every word earns its place with no redundancy.

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?

For a create-entity tool with a fully documented 8-parameter schema and an output schema present, the description provides enough context for selection and invocation. It could improve by explicitly referencing entity_create_text as the single-line alternative, but the core information is complete.

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 all eight parameters are already fully documented in the schema. The description only reiterates the width concept without adding new parameter semantics, so the baseline score of 3 applies.

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 uses a specific verb ('Create') with a specific resource ('multi-line text entity (MTEXT)') and adds a distinctive behavior ('word-wrap at the specified width'). This clearly differentiates it from sibling tools like entity_create_text, which creates single-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?

The description clearly conveys the tool is for multi-line text with word-wrap, which gives an agent contextual grounds to select it over entity_create_text or other create-entity tools. However, it does not explicitly state when not to use it or name alternatives.

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