Get pickup rates

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds that the tool returns specific pricing fields and does not spend money, which aligns with annotations but does not provide additional behavioral context beyond what annotations already convey.

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 two sentences with no extraneous words. The key action and return values are front-loaded. Every sentence adds value without redundancy.

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 the tool has 8 parameters, including nested objects, and no output schema, the description is minimal. It explains the purpose and return values but does not cover when to use each parameter or how to interpret the response. While the schema is detailed, the description could offer more context for effective use, especially given the presence of sibling quote tools like deershoot_get_parcel_rates.

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 100%, meaning the schema already describes all parameters. The description does not add any extra meaning or details beyond the schema, so it meets the baseline expectation.

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 explicitly states the verb 'Quote', the resource 'carrier pickup', and the specific return fields (id, base_price, fuel_price, final_price). It distinguishes from sibling tools like create_pickup_order or get_pickup by clarifying it is a quote that does not spend money.

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 notes 'Does not spend money' implying it's a non-destructive quote, but lacks explicit guidance on when to use this tool versus alternatives like deftship_create_pickup_order or deftship_arrange_pickup. No when-to-use or when-not-to-use information.

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