gcode_list_tools

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

The description discloses the core behavior (listing tools with first use line and usage count) but lacks details on what constitutes a tool reference, error conditions, or performance notes. Since no annotations are provided, the description carries the burden, and while adequate, it could be more comprehensive.

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, concise and front-loaded with the key action and output. No unnecessary words.

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?

Although the tool has an output schema (reducing the need to describe return values), the parameter ambiguity makes the description incomplete. For a simple listing tool, the minimum is met but not exceeded.

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 single parameter 'file_path_or_code' has 0% schema description coverage and the tool description does not clarify what it expects (file path vs. G-code string). This is a critical gap that prevents correct usage.

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 the tool's purpose: 'List all tools referenced in a G-code file, with first use line and usage count.' It uses a specific verb ('List') and specifies the resource ('tools in a G-code file'), distinguishing it from sibling tools like gcode_list_macros.

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 alternatives, such as gcode_list_macros. It does not mention any prerequisites, limitations, or context for selection.

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