object.create_text

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

Annotations already declare all hints as false, and the description adds no behavioral detail. 'Risk: standard' and 'maturity: L3' are operational metadata, not disclosures of side effects, state changes, output behavior, or prerequisites. The agent is left entirely unaware that this command mutates the scene.

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 text is short but not concise in a useful way; it repeats the command name and includes filler about risk and maturity that does not inform task execution. No purpose or parameter details are front-loaded, so the brevity is empty rather than 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?

For a tool with 8 parameters Secretariat preset and an output schema, the description is grossly incomplete. It reveals no functional outcome, no return payload, no side effects, and no conditions of use, making it inadequate for an agent to select or invoke the tool correctly.

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?

With schema description coverage at only 38%, the description must compensate, but it provides zero explanation of parameters like name, text, size, or extrude. The agent cannot infer parameter meaning or relationships from the description; it must rely on the bare schema types.

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 merely restates the command name `object.create_text` as 'PartMe Blender Harness command' and provides no verb, object, or outcome. It does not say the tool creates a text object, so an agent cannot determine its purpose from the 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 information about when to use this tool versus alternatives like blender_object_create_curve or blender_object_create_mesh. The only requirement mentioned is 'per-request argument checks and session policy', which is generic and not usage guidance.

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