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

Annotations already declare this a safe, idempotent read, and the description layers on real behavioral context: offers are immutable (sellers end and repost, so an ended offer beside a newer one is normal), pagination must be read rather than assumed, and status_counts is market-wide and unaffected by filters or page.

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?

Front-loads the core purpose and default status, then layers caveats; sentences are dense and mostly earn their place. It runs long, and the closing note about offer immutability, while useful, is the one part that could arguably move to a sibling tool's docs.

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 no output schema, the description carries the burden and does so: it explains the pagination block, the status_counts field, and default sort behavior. An agent has everything needed to call it correctly and interpret the result.

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%, so the baseline is 3, but the description adds meaning beyond it: most_completed is counted through the offer rather than the seller's whole history with newest tie-break, and search is scoped to title, description or seller username. It does not add anything for limit/offset beyond the schema.

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?

States a specific verb ('List') and resource ('standing offers on Freelance Clearing') and immediately scopes it to the Browse page's Offers-tab filters, which separates it from sibling list tools like browse_jobs and get_user_offers.

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?

Gives concrete when-to-use guidance for the status parameter ('pass status ended for the record of closed ones or any for both') and explains that the default matches the page default. It does not explicitly name a sibling alternative or say when not to use this tool, which keeps it short of a 5.

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