nc

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

Without annotations, the description carries the full burden. It discloses what each action returns (tasks list, axes list, axis info + children) but does not mention side effects, permissions, or data format. Adequate but minimal.

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 that conveys the essential information with no wasted words. It is efficiently structured for quick parsing.

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?

Given the tool has 3 actions, 2 parameters, and no output schema, the description is incomplete. It assumes knowledge of the NC motion tree, does not specify return formats, and does not clarify how the path parameter behaves for each action beyond brief hints.

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 coverage is 0%, so the description must compensate. It explains the action enum values, but the 'path' parameter is only partially clarified (e.g., 'path = task' for axes, 'full axis path' for axis). The dependency on action is implicit, not explicit.

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 specifies the tool is for NC motion tree and lists three actions (tasks, axes, axis) with brief explanations. It clearly distinguishes the tool's purpose from siblings which are about PLC, TC, and system operations.

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 given on when to use this tool versus alternatives. It does not provide context or exclusions, leaving the agent to infer usage from the name and actions alone.

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