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

No annotations are provided, so the description carries the full behavioral burden and does so richly: court service mechanics (inbox/URL, deemed served on first read or after 72 hours), the countersign/dispute window at a named endpoint, silence meaning acceptance, no entry on the supplier's record, and the auth requirement ('Enrolled agents only'). This is exactly the kind of consequence and auth disclosure the annotations would otherwise supply.

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 roughly 200 words of dense legal prose with repeated citations (PD14 §2/§3/§12 referenced multiple times) and nested parentheticals. The core purpose statement is buried behind a scenario preamble, so it is not front-loaded, and the operator/Clerk branch is packed into one long sentence. Much of the statutory citation is not actionable for an agent.

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 complex, nested-schema mutation with no output schema, the description covers the process and outcomes well (contract on record, supplier countersign/dispute path, operator variant). With no output schema it appropriately narrates what results. It leaves a few parameters (ref, form, currency) undocumented, keeping it from a 5.

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 description coverage is 44%, so the description must compensate. It does add meaning to the two non-obvious parameters – rail ('your lodgement with a rail is your acceptance') and forOperator (deemed acceptance, operator as payee) – but ref, form, currency, and priceCents receive no explanation in either place. Partial compensation, so a baseline-ish 3.

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 gives a specific verb+resource: 'Lodges the quote as its buyer, naming the supplier and the rail you pay by.' The opening scenario ('An agent quoted me a price and did not lodge it') clearly frames a distinct job from a plain self-lodged quote. It stops short of explicitly naming or contrasting with the sibling lodge_quote, so it isn't a clean 5.

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?

It supplies a concrete triggering scenario ('quoted me a price and did not lodge it; I want it on the record anyway') and a constraint (enrolled agents only). It also notes the fallback ('A supplier that disputes having quoted ... file an ordinary claim on your own evidence'). No direct when-not/alternative-vs-lodge_quote routing is stated, so not a 5.

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