object.create_mesh

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

The description provides no behavioral information about the tool's effects, side effects, permissions, or output. Annotations indicate it is not read-only, not destructive, not open-world, and not idempotent, but the description does not add any context such as what happens to the scene or whether it requires specific conditions. It only states risk and maturity, which are unrelated to behavior.

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 concise in length but severely under-specified. It is a single sentence that repeats the command name and adds generic metadata, making it a tautology rather than a meaningful description. The lack of substance outweighs any brevity benefit.

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 9 parameters, 3 required, and an output schema, this description is completely inadequate. It does not explain the tool's purpose, expected inputs, or behavior, leaving an agent to rely solely on the name and schema. The description fails to provide the context needed to correctly invoke this tool, especially given the complex transaction and authorization parameters.

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 description contains zero information about any of the 9 parameters. Schema description coverage is 67%, so some parameters are partially documented in the schema (e.g., scale, location, rotation have descriptions), but the description does not clarify the 'primitive' parameter or any others. It does not compensate for the schema's incomplete coverage, and the odd 'rotation uses radians' note on scale/location could confuse an agent.

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 essentially a tautology: it only restates the command name 'PartMe Blender Harness command `object.create_mesh`' without explaining what the tool does. It does not mention that it creates a mesh object or differentiate from siblings like blender_object_create_curve or blender_object_create_text. The name itself is somewhat self-explanatory, but the description adds no functional purpose.

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. The description only mentions risk, maturity, and generic requirements ('Per-request argument checks and session policy still apply'), none of which help an agent decide when to invoke this command. No context about typical workflows or exclusions is provided.

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