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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description nonetheless adds genuinely non-structured context: it requires a paid subscription, is scoped to the caller's own records, and explicitly excludes live orders and model inference, which usefully bounds what the results contain.

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?

Four short sentences with the resource and scope front-loaded, and no filler. The access line ("keyless: subscription_required with a subscribe link") is slightly compressed to the point of awkward double-colon phrasing, but it stays brief and informative.

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 zero-parameter, read-only list tool with full annotation coverage, the description supplies what matters: what is listed, whose records, cost/access gating, and what the results do not include. It omits result shape and ordering/pagination behaviour, which is a modest gap given there is no output schema.

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 input schema defines zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description's scope statement (owned records only) is consistent with a zero-argument tool that implicitly filters to the caller.

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 ("List owned saved studies") and adds scope (owner-only, paid tier). It does not, however, distinguish itself from neighbours like research_run_read or research_paper_list, and the name says "runs" while the description says "studies", leaving a small terminology gap an agent must bridge.

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?

Usage is implied: retrieve your saved research runs. There is no explicit when-to-use versus research_run_read (single run) or research_paper_list, and no stated preconditions beyond 'paid, owner-only'. An agent can infer the listing use case but gets no routing guidance.

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