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

The description discloses key behaviors: kernel-free generation, deterministic (no model call), and the guarantee that non-watertight STL fails the call with MESH refunded. It also mentions the cost (15 MESH/call). Annotations indicate readOnlyHint=false and openWorldHint=true, which align with the description's emphasis on deterministic generation and no model call. The description adds value beyond annotations by explaining failure modes and guarantees.

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, front-loaded with the core purpose, and every sentence adds value. It covers purpose, guarantees, failure behavior, determinism, and cost in a compact format. No wasted 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?

Given the complexity of the tool (many parameters, multiple output formats, guarantees), the description is quite complete. It explains the output formats, the guarantee of wall thickness, failure handling, and determinism. It does not detail return values, but there is no output schema, so the description could have mentioned what the response contains (e.g., base64 STL). However, the description mentions 'binary STL (watertight solid), DXF R12, or SVG' and 'MESH refunded' which gives some context. Slight gap on response structure, but overall adequate.

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 input schema has 100% description coverage for all parameters, so the description does not need to add much. However, the description does not provide additional context beyond the schema, such as relationships between parameters (e.g., wall must be less than pitch) which are already in the schema. The description mentions 'Full input contract: this tool's input_schema' which reinforces reliance on schema. Baseline 3 is appropriate.

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: turning parameters into manufacturable files (STL, DXF, SVG) for parametric lattice/perforation panels. It specifies the exact output formats and the guarantee of wall thickness, distinguishing it from generic file generation tools. The verb 'Turn' and resource 'parameters into a manufacturable file' are specific and actionable.

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 implies usage for fabrication tasks (3D printing, laser cutting, CNC) and mentions deterministic behavior, but does not explicitly state when not to use it or suggest alternatives. It provides clear context for when to use this tool, but lacks explicit exclusions or alternative tool references.

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