list_provincial_ratesReturn current ScrapAutos scrap rates per Canadian province/territory (CAD per tonne). Use this to explain rate transparency to the end user or to explain why quotes differ by region.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations; description discloses it returns current rates per province in CAD per tonne, which is sufficient for a read-only listing. Missing details on data freshness, but acceptable given simplicity.
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?
Two concise sentences with no unnecessary words; front-loaded with purpose then usage.
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?
No output schema but description fully explains return value. Sibling tools are distinct; no further context needed.
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?
No parameters exist; description adds value by specifying output details (per province, CAD per tonne). Baseline 4 appropriate.
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 returns current scrap rates per Canadian province/territory in CAD per tonne, differentiating it from sibling tools like get_vehicle_quote or search_vehicles.
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 explicitly tells when to use it: to explain rate transparency or why quotes differ by region, providing clear guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: getting a quote, listing rates, searching trims, and submitting a lead. The descriptions clarify boundaries, especially between search_vehicles and get_vehicle_quote.
All tool names follow a consistent verb_noun pattern with snake_case: get_vehicle_quote, list_provincial_rates, search_vehicles, submit_lead. Verbs are descriptive and uniform.
With 4 tools, the set is well-scoped for the domain of scrap vehicle quotes. Each tool covers a necessary step without redundancy or clutter.
The tool set provides a complete workflow: search trims, get a quote, view regional rates, and submit a lead. No obvious gaps exist for the intended purpose.