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 adds genuinely new context beyond them: paid tier, owner-only scope, and a keyless subscription_required access gate with a subscribe link. It stops short of describing whether results are paginated or empty-list behavior for non-subscribers.

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?

Three short sentences with the subject front-loaded and zero filler; scope, billing/ownership, and access gating each get exactly one clause. Nothing is repeated from the annotations or schema.

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 there is little to document, and the access and ownership constraints are stated. With no output schema, however, the description never indicates what an account record contains or in what form the list returns, leaving the agent to discover return shape empirically.

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 nothing for the description to disambiguate and the schema is trivially complete. Baseline 4 applies; no parameter-level ambiguity exists.

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 reference paper accounts.' That clearly separates it from mutating siblings such as research_paper_start or research_paper_archive and from research_paper_read. The term 'reference paper accounts' is somewhat jargon-laden, so an agent still has to infer whether an 'account' is a workspace or a paper-trading entity.

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 the discovery role ('List owned ... accounts') and warns there are 'No live orders or model inference,' which frames the context. It never explicitly contrasts with research_run_list or research_paper_read, so the agent must infer when this list is the right entry point versus a run listing.

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