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

Annotations already declare it read-only, idempotent, non-destructive and closed-world, yet the description adds real behavioral context beyond them: the privacy model for requests (private between buyer and seller, only your own readable), and that completed_through/transacted_through are offer-scoped rather than lifetime totals. This is disclosing data semantics and access boundaries an agent could not infer from the annotations.

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-loaded with the action, then spends its length on field semantics that the missing output schema would otherwise leave unexplained, so the detail largely earns its place. It is dense and clause-heavy, but not padded with restatements of the name or annotations.

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 full burden of explaining return values, and it does: it defines completed_through, transacted_through, completed_jobs, buyer ratings per job, and offer_job_number's ordering and role as the only row identifier. It also clarifies the privacy boundary and the tool to use for requests, leaving no material gap for a read of a single offer.

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% and the single offer_id parameter is fully documented as a UUID with a pattern in the schema. The description adds no syntax or format detail beyond 'one offer,' so it does not exceed what the schema already provides — the baseline 3 for a fully-covered single parameter is correct.

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 and resource (fetch/read one offer in full) and pins down the scope: the seller's figures plus the offer's own record. It also distinguishes what it does NOT return (requests) and names the sibling that does, so an agent knows exactly which tool covers which data.

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 an explicit exclusion and alternative: requests are not here, and 'you read your own through get_my_requests.' That cleanly routes one ambiguous case, though it never states how to choose between this and its closer siblings like browse_offers or get_user_offers.

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