Maya Command

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

No annotations exist, so the description carries the full burden, and it discloses only that batches are grouped into one undo chunk. It says nothing about whether commands mutate the scene, what permissions or context (main thread, open scene) are required, what happens when one command in a batch fails (partial application vs. rollback), or how errors are surfaced.

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?

A single front-loaded sentence with no filler, and the key scope statement comes first. It is efficient, though its brevity is arguably under-specification rather than disciplined concision given the tool's risk profile.

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?

An output schema exists, so return values need not be explained, and the undo-chunk note covers the most surprising side effect. But for an arbitrary execution escape hatch with four undocumented parameters and no annotations, the description leaves too much for the agent to infer before calling.

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% across four parameters, so the description must compensate and does not. It hints at a single-vs-batch distinction ('one command or a batch') but never maps that to 'command'+'args'+'kwargs' vs. 'commands', nor says whether the two forms are mutually exclusive or what shape a batch entry takes.

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 ('Execute') and resource ('one native maya.cmds command or a batch'), which clearly distinguishes it from the read-only scene_* siblings. The scope is understandable without opening the schema, though 'native maya.cmds' assumes the agent knows what that surface covers.

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 versus the structured siblings (scene_context, scene_hierarchy, etc.) or when a batch should replace two single calls. The only implicit cue is 'batch ... single undo chunk', which is a behavior, not a selection rule, and no exclusions or prerequisites are given.

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