Get Order Amount

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

With no annotations, the description must fully disclose behavior. It states the tool calculates cost but does not mention whether it is read-only, idempotent, or if it has side effects. No information on authentication, rate limits, or error scenarios is provided.

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 extremely concise with two short, direct sentences. No unnecessary words or filler. It efficiently conveys the core purpose and a key usage hint.

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?

Given 7 parameters and no output schema or annotations, the description is too sparse. It does not explain the return format (likely a numeric amount), error handling, or how this fits into the ordering workflow beyond 'before payment'. More context would be needed for an agent to use it correctly without extra assumptions.

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 covers 100% of parameters, so the baseline is 3. The description adds the context that parameters match create-order, which is useful but does not provide additional meaning beyond what the schema already offers (e.g., descriptions for each parameter are in the schema itself).

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 verb 'calculate' and the resource 'cost of an order', making the tool's purpose unambiguous. It references 'create-order' for parameter similarity, but does not explicitly distinguish itself from sibling tools like create-order itself, leaving room for slight confusion.

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 before payment by stating 'before payment', and notes parameter overlap with create-order. However, it does not specify when not to use this tool or provide alternatives (e.g., get-balance for account balance). The guidance is clear but incomplete.

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