What the person owns

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description earns credit by disclosing the actual contents of the result (tier, file fields, zip flag, latest update) in the absence of an output schema, though it says nothing about result size, pagination, or what happens for an empty library.

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 sentences, front-loaded with scope, and the parenthetical field list earns its space because no output schema exists. The follow-up routing sentence is short and actionable; nothing is padding.

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 carries the return-value burden and does so by naming the key fields. Minor gaps remain: no statement about result volume or whether the list is ever truncated, and no explicit tie-break against the other listing 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?

The tool takes zero parameters, so there is no parameter semantics to explain; baseline 4 applies. The description correctly implies the call is argument-free by framing the result as everything the person owns.

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?

Opens with a specific scope statement ("Every product the person owns") and enumerates the payload: product card, tier, file metadata, zip availability, latest update. Clear verb+resource. It does not explicitly distinguish itself from search_products or list_shelves, which keeps it off a 5.

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?

Implies a workflow by saying "File ids go to download_to_folder or get_download_links," which tells the agent what to do after this call. It gives no guidance on when to prefer this over search_products or list_shelves, and no exclusions or prerequisites.

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