get_post_processing_guide

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

No annotations provided, but description explains what is returned (techniques, paintability, strengthening with steps, tools, difficulty, safety). No side effects or permissions noted, but adequate for a read-only guide.

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?

Concise, well-structured with purpose, return content, usage examples, and parameters. Every sentence adds value; no redundancy.

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 one required parameter and no output schema, the description covers input and output adequately. Could mention return format, but not essential for this 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?

Schema has 0% coverage for the 'material' parameter. Description adds examples of Material IDs ('pla', 'abs', 'petg', 'nylon'), providing meaningful guidance beyond the schema.

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 it retrieves post-processing techniques for a 3D printed part, listing specific techniques like sanding, painting, and strengthening. It distinguishes from siblings by focusing on finishing, not material properties or printing.

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?

Provides explicit example queries ('how do I make this print look better?', 'can I paint PLA?') indicating when to use. Lacks explicit exclusions or alternatives, but examples give strong context.

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