get_fee_breakdown

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It states the tool 'reads' (implying read-only) and lists fee types, but it does not mention data freshness, error handling (e.g., missing ASIN), or whether the breakdown is current or historical. Minimal additional context beyond the basic purpose.

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 sentence of 13 words, front-loading the purpose and listing fee types. Every word contributes to understanding, 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 simple tool with one parameter and no output schema, the description is bare. It explains what the fee breakdown includes but omits the response structure, any limitations, or how it relates to sibling tools. The agent lacks information to set expectations for the return value or to handle edge cases.

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 schema has 0% description coverage, and the description adds no semantic meaning beyond the parameter name 'asin'. It simply says 'for an ASIN', which repeats the schema. The AI agent gains no understanding of what an ASIN is, its format, or constraints.

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 Amazon fee breakdown for an ASIN, listing specific fee types (referral, FBA, storage, dimensional weight). It is a specific verb+resource combination, but it does not explicitly distinguish itself from sibling tools like get_profitability or get_fba_inventory, which may also contain fee-related data.

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 provides no guidance on when to use this tool vs alternatives, nor does it mention prerequisites or exclusions. It merely states what it does, leaving the AI agent to infer context from the tool name and sibling list.

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