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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely useful context — the X-Mako-Key auth requirement and the fact that only completed deliverables are returned — but says nothing about ordering, pagination, or result shape.

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 tight sentences with the scope front-loaded before the auth note; no filler. It could be marginally sharper by folding the auth requirement into a usage clause, but it is well sized for the operation.

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-only list tool with no output schema, the description conveys what is returned at a high level and the auth prerequisite. It stops short of paging/limit behaviour and the client-account scoping, which an agent calling it with three optional params would benefit from knowing.

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 33%, so the description must compensate. It loosely maps the kind enum values (competitor report bundles, May run artifacts) but adds nothing for limit and never explains the client_account_id narrowing, so half the parameters remain opaque in both description and 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?

The description gives a specific verb (List) and resource (deliverables) and enumerates the two content types returned: competitor report bundles and May run artifacts. It does not, however, explicitly contrast itself with adjacent siblings such as get_download_url or order_report, so an agent must infer the boundary.

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?

It says what is listed ('finished and ready to download') but never states when to call this versus get_download_url (the obvious next step) or order_report/run_may (which produce the artifacts). There are no stated conditions or exclusions, only implied usage.

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