Get PrintYourDuck Quote Requirements

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context by specifying what types of information are returned (file types, materials, etc.) and explicitly stating the tool does not calculate instant pricing, which prevents a common misconception.

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 two sentences long and front-loads the core purpose, then adds the usage timing, a list of content areas, and a crucial exclusion. Every sentence earns its place with no fluff or repetition.

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 zero-parameter read-only tool with annotations and an output schema, the description is complete. It tells the agent when to use the tool, what it will find, and what it will not do. Nothing essential is missing.

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 tool has zero parameters and schema coverage is 100%, so there is no parameter ambiguity. The description appropriately compensates by explaining the purpose and scope of the data returned, making it clear what the agent will receive when invoking the tool.

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 reads public requirements for a PrintYourDuck manual custom 3D printing quote request. It lists specific content areas (file types, material options, confirmations, restrictions, private-upload flow) and distinguishes it from instant pricing tools. This is a specific verb+resource combination that clearly differentiates it from siblings like get_quote_status.

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 explicitly says 'Use this before submitting local files' and enumerates what to check, providing clear when-to-use context. While it doesn't name alternative tools, the timing guidance and the negative statement 'Does not calculate instant pricing' help an agent decide when not to use it.

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