blender_annotation_text

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

With no annotations, the description carries the behavioral burden. It clearly states the core behavior—creating a font/text object—but leaves gaps such as object naming, orientation/units, and whether it appears in the active collection.

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?

Two sentences with no filler, front-loaded with the action and resource. Every clause adds value.

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 simple parameterized creation tool, the essentials are present and the schema covers the inputs. It falls short on return value/object name and on disambiguation from the several sibling annotation tools, so a bit more context would help.

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?

The schema already documents all four parameters, including defaults for size and color, so the description adds no extra parameter meaning. Baseline 3 applies because schema coverage is 100%.

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?

States a specific verb and resource ('Add a 3D text annotation at a specific location') and clarifies that it creates a font/text object. It is clearly about text annotations rather than generic annotations, but it does not explicitly differentiate from nearby siblings like blender_annotation_add or blender_grease_pencil_create.

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 'label or callout' phrase gives an implied use case for when this tool is appropriate. However, it provides no explicit guidance on when to choose this over blender_annotation_add, blender_annotation_dimension, or grease pencil tools.

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