maya_command_help

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

No annotations are provided, so the description carries the full transparency burden. It uses 'gets' and 'retrieves' implying a read-only operation, which is appropriate for a help tool. It does not mention side effects (none expected) or error handling, but for a simple lookup tool this is adequate.

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: two sentences for purpose/usage, followed by a clean Arg block. The main purpose is front-loaded in the first sentence, and every sentence adds value. No unnecessary words or repetition.

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 one required parameter and no output schema, the description covers all necessary context: what it does, when to use it, why it's needed, and parameter semantics with examples. It is fully self-contained for an agent to invoke 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?

The schema has 0% description coverage, but the description explicitly defines 'name' as the command name and gives three concrete examples ('polyBevel', 'skinCluster', 'polyProjection'). This fully compensates for the missing schema description and provides clear meaning beyond the parameter name.

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 clearly states 'maya.cmds 명령 하나의 플래그 목록과 시그니처를 가져옵니다' (gets the flag list and signature of a single maya.cmds command). This specifies a clear verb and resource, and distinguishes from siblings by limiting to a single command (contrasting with search/execute tools).

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?

The description explicitly says to call it before writing code when flag names or argument formats are uncertain, and gives a reason (Maya versions differ, memory is unreliable). It provides clear when-to-use context, but does not mention alternatives or when-not-to-use, so it falls short of a 5.

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