validate_gcode_safe

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

The description explains that validation uses printer-specific safety profiles and falls back to generic defaults. However, it does not disclose whether the tool is read-only (e.g., does it alter any state?) or what happens on validation failure (e.g., throws error, returns list of issues). Without annotations, more detail would be beneficial.

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 and well-structured, with the purpose stated upfront followed by usage guidance and parameter details. It avoids unnecessary verbosity while covering key points, though the Args section slightly repeats schema information.

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 lack of output schema and annotations, the description covers the core functionality, usage, and parameter semantics. However, it does not explain the return value (e.g., validation errors or pass/fail) or edge cases like empty commands. For a validation tool, this is adequate but could be more comprehensive.

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 for parameters, but the description adds meaning by stating that 'commands' are G-code separated by newlines and 'printer_id' is an optional model ID for profile-aware validation. This provides necessary context beyond the schema's type and title.

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 validates G-code with printer-specific safety limits like PTFE temp caps and speed limits. It explicitly distinguishes itself from the sibling validate_gcode by being preferred when the target printer is known, making the purpose unambiguous.

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 explicit usage guidance: it is preferred over validate_gcode when you know the target printer, and it falls back to conservative generic defaults if printer_id is omitted. This clearly indicates when to use this tool versus alternatives.

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