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

With no annotations provided, the description carries the full burden. It discloses fixed fee rates ($0.20 listing, 6.5% transaction, 3%+$0.25 payment) and notes the fee breakdown is always visible, adding valuable behavioral detail beyond a generic 'calculate'.

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 a single concise sentence with a supplementary clause about fee breakdown. It front-loads the core purpose and avoids any 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?

The description mentions the key outputs (net proceeds, break-even price) and fee formula, which is helpful. However, it does not address the six required input parameters, and with no output schema or annotations, the overall guidance is incomplete for an agent to invoke it correctly.

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 description coverage is 0%, and the description does not explain any of the six required parameters (e.g., cogs, offsiteAds, processingRatePct). The only values mentioned are fixed fee rates, not input parameters, so the description fails to compensate.

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 function with a specific verb ('Calculate') and resource ('Etsy fees, net proceeds, and break-even price'). The Etsy-specific scope distinguishes it from the many generic calculators among sibling tools.

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 clear usage for any Etsy listing, but does not explicitly state when to use it over alternatives or provide exclusions. The context is unambiguous enough for a calculator tool.

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