shopify_fee_calculator

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

No annotations are provided, so the description must fully disclose behavior. It only lists fee rates but does not explain what the tool outputs (e.g., total monthly fee, per-transaction fee breakdown, or both). It also doesn't mention if monthlySales is required for per-transaction fee calculation or if it's optional. The description is too sparse to convey the tool's actual behavior beyond the fee schedule.

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 that front-loads the key information (monthly fees and per-transaction rates). It is efficient and to the point, with no unnecessary words. However, it could be slightly more structured (e.g., separating monthly and transaction fees) but overall it is appropriately sized.

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 tool has 2 parameters, no output schema, and no annotations, so the description must be robust. It only covers the 'plan' parameter's fee schedule, leaving 'monthlySales' unexplained. It also doesn't clarify what the output is (e.g., total cost, breakdown). Given the tool's purpose is to calculate fees, missing sales parameter semantics is a major incompleteness.

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 0% description coverage, so the description must compensate. The description maps the 'plan' parameter to the three plans (basic/shopify/advanced) with associated fees, but it does not explain the 'monthlySales' parameter at all. This is a significant gap: the description leaves the purpose of monthlySales ambiguous, which is critical for correct invocation.

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 that this tool calculates Shopify monthly fees and lists the specific monthly and per-transaction fee rates for each plan. It is named 'shopify_fee_calculator' and the description aligns with this purpose, making it distinguishable from other platform fee calculators like PayPal or Etsy. It could be more explicit in saying 'calculates' but the fee rates make the purpose evident.

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: given a Shopify plan (and optional monthly sales), it returns the fees. However, it does not explicitly state when to use this over the sibling calculators (e.g., when the merchant is on Shopify) or any exclusions (e.g., not for other platforms). The presence of sibling calculators like 'platform_fee_comparison' suggests a need for routing, but no guidance is provided.

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