create_text

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It offers none—no mention of what the tool does, what it returns, side effects, or any preconditions in Blender. The description is merely the name, giving zero behavioral information.

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 short, but this is under-specification, not conciseness. The single sentence merely restates the tool name and provides no value. It does not earn its place; it could be removed without loss.

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 creates a text object with multiple parameters and has an output schema (contents unknown), the description is wholly inadequate. It provides no context about the effect, usage, or returned data. An agent would be completely in the dark.

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 0%, meaning the schema does not explain parameters. The description also provides no explanation for the five parameters (body, name, size, extrude, location). An agent cannot infer what these parameters mean or how they affect the text object from the description.

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 is 'Blender Studio Pro MCP: create_text', which is essentially a restatement of the tool name with a prefix. It does not state what the tool does—no verb, no resource, no action beyond the implied 'create text' in the name. This is a tautology and fails to distinguish it from siblings like set_text_body or create_curve.

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?

There is no guidance on when to use this tool versus alternatives. No mention of scenarios where creating a text object is appropriate, or when to use set_text_body instead. The description provides no context for selection.

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