object.create

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

The description does not disclose any behavioral traits beyond the basic action. Since no annotations are provided, the description should convey important details like whether it affects the current selection, scene, or returns a reference. It fails to do so, leaving the agent uninformed about consequences.

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 a single sentence, making it concise and front-loaded with the verb 'Create'. However, it is too brief and lacks essential details, making it less helpful than it could be. Every sentence should earn its place; here, it's under-specified.

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?

With 18 parameters, no output schema, and no annotations, the description fails to provide necessary context. The tool is complex (multiple primitive types, many options), yet the description only gives a high-level overview. Complete guidance is missing, making it inadequate for correct invocation.

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 description must compensate, but it adds no parameter information. The 18 parameters are entirely undocumented in the description, forcing the agent to rely solely on schema titles, which are limited. This is a critical gap.

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 'Create a common mesh primitive or empty' clearly indicates the tool's purpose: it creates a primitive mesh object or an empty. The verb 'Create' is specific, and it distinguishes from sibling tools like object.duplicate or object.delete. However, it could be more explicit about what 'common mesh primitive' includes.

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 guidance is provided on when to use this tool versus alternatives. With many sibling tools (e.g., mesh.extrude, object.duplicate), the description lacks context about scenarios where object.create is appropriate, and no exclusions or conditions are mentioned.

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