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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description's one added behavioral fact is the admin-only authorization requirement, which is genuinely useful but is the sole contribution; nothing is said about result size, pagination, or scoping.

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?

A single short sentence with no filler and the resource named up front, which is good structure. However, the sentence is verbatim identical to the title, so it consumes the entire description budget without adding any new information beyond the admin restriction.

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?

The description usefully signals what the listing contains (documents, their fill-ins, packets, published version), which partly substitutes for the missing output schema. It is nonetheless silent on the sole input parameter, result volume/pagination, and how the library scope differs from sibling list tools.

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?

There is one optional parameter (request_id) at 0% schema description coverage, and the description says nothing about it at all. With coverage this low the description is expected to compensate, but it neither explains request_id nor any filtering/formatting behavior.

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?

The only usage-relevant clause is 'Admins only', which is an authorization precondition rather than a when-to-use rule. There is no guidance on when to choose this over yardstick_offers_documents_list or yardstick_offers_library_documents_read, and no exclusions or prerequisites beyond the admin restriction.

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