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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds nothing beyond that except the describe_operation pointer; it does not describe what is returned, whether results are scoped to the caller's workspace, or any rate/size limits.

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?

It is short, but the one substantive sentence is duplicated verbatim, and the internal operation ID adds noise rather than information. There is no front-loaded statement of what the call does.

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?

No output schema and no documentation of the free-form query object, so an agent cannot tell what fields exist to filter on or what shape the response takes. For an open-ended list endpoint, the description leaves the essential calling information missing.

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?

Two parameters (query, params) with 0% schema description coverage and an open-ended additionalProperties object; the description offers no parameter names, formats, or filtering semantics. With coverage this low, the description needed to compensate and does not.

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 restates the endpoint path "GET /api/letterheads" twice, which is essentially a tautology of the name and title. It never says in plain language that this lists/returns letterhead resources, what a letterhead is, or how it differs from the many other GET list tools.

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 routing hint is that "describe_operation provides native request schemas," which points at a sibling but gives no condition for choosing this tool or for when not to use it. There is no guidance on prerequisites, filtering, or pagination.

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