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

No annotations are provided, so the description carries the full burden. It discloses that the price is a live estimate matching the calculator, includes VAT, and is subject to change after survey. No destructive or mutable behavior is implied, sufficient for an estimation tool.

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 front-loaded with the core purpose, but includes bilingual text (Hungarian and English) which, while helpful, adds some redundancy. Overall it is efficient and logically structured.

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 price estimation tool with a complete input schema, the description covers the purpose, usage scope, and constraints. No output schema exists, but the description clarifies the output is a gross price. Minor omission: does not specify the output format (e.g., currency unit), but the core information is present.

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 coverage is 100%, and the description adds value by explaining the context: 'type' maps to window/door, 'color' includes examples, 'glazing' indicates double/triple, and dimensions are for custom sizes. It also links 'door' to custom Aluplast doors, reinforcing the sibling distinction.

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 provides a gross (VAT-inclusive) price for custom-size plastic windows or doors, using a live calculation matching the Genesis editor. It distinguishes from siblings by explicitly noting that standard inventory doors are handled by list_inventory.

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 explains when to use the tool (custom-size windows/doors) and when not (standard CanDo doors, which are priced separately via list_inventory). It also notes that the final price is determined after on-site survey, setting expectations correctly.

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