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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds one genuinely useful behavioral fact not in the annotations: output detail is permission-dependent (members see status only; creator and admins see full details). It says nothing about how request_id behaves, what include_archived does, or what happens for a nonexistent or unauthorized offer.

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 short sentences, front-loaded with the action and followed by the permission caveat; no filler. The brevity is efficient even though it leaves informational gaps that are penalized elsewhere.

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 read tool with three parameters at 0% schema coverage and no output schema, the description leaves the two optional parameters entirely unexplained and gives no hint of the returned shape beyond the visibility clause. An agent cannot safely decide when to pass request_id or include_archived from this text.

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 0% across three parameters, so the description must compensate, and it does not: neither request_id (likely a deduplication/request key) nor include_archived is mentioned. Only the offer_id is weakly implied by 'Read an offer'.

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?

Tautological: description restates name/title.

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?

Usage is only implied: it reads a single offer, so the agent infers it needs an offer_id. There is no explicit when-to-use, no mention of when yardstick_offers_list, yardstick_offers_status, or yardstick_offers_timeline would be the better call.

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