alonomic_calc_parcel

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

With no annotations, the description must carry the burden. It states read-only and non-creating behavior, and lists response fields, but does not disclose auth needs, rate limits, or other side effects. Adequate but not rich.

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?

Efficiently conveys purpose, endpoint, and parameter details in a short paragraph. Front-loaded with main purpose. Could be slightly more concise, but no wasted sentences.

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?

With output schema present, description only needs to highlight key return fields, which it does. Covers all parameters with adequate detail for a nested-object tool. Leaves little ambiguity.

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 0%, so description compensates fully by explaining each parameter's content (drop address structure, parcel fields, optional pickup details, instance). Adds meaning beyond vague schema types.

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?

Description states specific verb 'Estimate' and resource 'parcel's price and dimensions', and explicitly says 'read-only' and 'Does NOT create a parcel', clearly distinguishing from sibling 'alonomic_create_parcel'.

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?

Explicitly states that the tool is read-only and does not create a parcel, providing clear context for when to use (estimation) vs. alternative creation tools. However, lacks explicit when-not or other alternative names.

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