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

Annotations already cover safety (readOnly, non-destructive, non-open-world), so the description earns credit for adding behavior beyond them: the response encoding (base64 for images and PDFs) and the retention guarantee that the link keeps working after the plan ends. Neither detail is derivable from annotations or schema.

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 no filler; the primary function is front-loaded and the parenthetical return-format detail and retention caveat both earn their place.

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 supplies the key return shape (text vs. base64) and a persistence guarantee. It stops short of covering edge cases like an empty/unpublished link or how large base64 payloads are delivered, which would matter for a read tool.

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% with clear descriptions for instance_id ('from buy or list_utilities') and passport_token, so the schema carries the parameter burden. The description adds nothing about either parameter, making baseline 3 appropriate.

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 ('read back what is published on your share link') and clarifies the return encoding for text vs. binary assets. It implicitly pairs with the sibling share_set, though it never names the counterpart explicitly.

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 read direction is implied by 'read back' and contrasted with publishing, but there is no explicit when-to-use/when-not guidance or named alternative. The 'works after the plan ended too' note gives a useful condition under which it still applies.

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