maya_create_primitive

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

Without annotations, description carries full burden but only states basic action. Does not disclose side effects (e.g., naming conflicts, undo behavior), or behavior when position/scale/rotation are omitted.

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?

Single sentence with verb and object front-loaded. Concise, but could include a brief usage note (e.g., naming defaults).

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?

Output schema exists (not shown), so return value explanation unnecessary. Lacks guidance on integration with other tools or error handling, but sufficient for basic use.

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?

Input schema has descriptions for each parameter (0% coverage context likely refers to top-level, not nested). Description adds no extra meaning beyond summarizing optional parameters. Baseline 3 as schema already provides meaning.

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?

Description clearly states verb 'Create', resource '3D primitive', and lists all supported types (cube, sphere, etc.). This distinguishes it from sibling tools like maya_create_camera and maya_create_light.

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 on when to use this tool versus alternatives (e.g., maya_mesh_operation for modifications). No mention of prerequisites or context.

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