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

Annotations already cover readOnly/idempotent/non-destructive/closed-world, and the description goes further by disclosing the paper:read permission prerequisite, that note excerpts are bounded and explicitly labeled when truncated, and that cursors are opaque page positions. These are real operational details the annotations do not convey; a 4 rather than 5 only because rate limits, page-size behavior, and error cases remain unstated.

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?

Five dense sentences, purpose front-loaded, each carrying distinct information (kinds, truncation labeling, permission, query semantics, pagination). No filler, though the excerpt/content sentence sits slightly awkwardly before the permission note.

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 an output schema present, return values need not be described, and the description adds the permission gate, truncation disclosure, and pagination semantics an agent needs. Only the limit parameter and any per-kind difference in returned content are left thin.

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 0%, so the description carries the burden, and it does explain 'Search matches titles' for query and 'cursors are opaque page positions' for cursor, and it enumerates the three kind values. However, limit is never mentioned and per-kind matching behavior is left ambiguous, so it only partially compensates for the coverage gap.

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?

Clear verb (List) plus a specific resource set (saved strategies, simulation runs, or research notes) that maps directly to the kind enum. It implicitly distinguishes itself from get_strategy and save_research_note by framing this as paged enumeration of saved items, but it never names a sibling outright, so it stops short of 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?

'Paper runs require the separately approved paper:read permission' and 'Search matches titles' give situational context for two of the kinds, but there is no explicit when-to-use-this-vs-get_strategy/get_run_report guidance and no when-not conditions. Usage is implied rather than spelled out.

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