mastercam_help

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the scope (tools and safety levels) but does not describe additional behaviors such as return format or that it provides an overview. It is consistent with annotations and adds minimal value beyond them.

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, focused sentence with no extraneous words. It front-loads the core purpose and is appropriately concise for a help tool.

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 no-parameter help tool, the description is mostly complete. It explains the tool's function and mentions safety levels. However, given the large number of sibling tools, it could benefit from a note on when to use it as an entry point versus the more specific capability tools, but this is not critical for a simple help tool.

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?

There are 0 parameters, so the input schema is empty and requires no explanation. The description does not need to elaborate on parameters; the baseline of 4 applies since there are no parameters to describe.

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 states a clear verb ('Explain') and resource ('Mastercam MCP tools and safety levels'), which is specific and informative. However, it does not explicitly differentiate from siblings like 'mastercam_capabilities' or 'discover_capabilities' that may overlap in purpose; the mention of 'safety levels' provides some distinction but could be clearer.

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 provides no guidance on when to use this tool versus the many sibling tools. It does not mention any prerequisites, alternatives, or conditions for selection, leaving the agent to infer when this is the appropriate choice.

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