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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), yet the description adds real context: truncated excerpts are explicitly labeled, saved text is user-authored, paper runs need separate permission, and cursors are opaque. It does not describe page-size behavior or error cases, so it stops short of a 5.

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?

Front-loaded with the core action, then dense supporting facts in four short sentences with no filler. Slightly packed with tangential notes (user-authored content, permission caveat), but each sentence carries information.

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-value explanation is not required, and the description covers pagination model, search semantics, truncation labeling, and the permission gate. An agent could invoke it correctly; only page-size limits and kind-specific behavior are left implicit.

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 description coverage is 0%, so the description must carry parameter meaning. It clarifies query (matches titles) and cursor (opaque page positions), but says nothing about kind values beyond the enum or about the limit bounds (1-20) documented only in the schema, leaving two of four parameters thinly covered.

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 with enumerated scope: 'List a page of saved strategies, simulation runs, or research notes in the connected workspace,' matching the kind enum. It is easy to distinguish from siblings like get_strategy or save_research_note, though it does not name an alternative 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?

It gives a prerequisite ('Paper runs require the separately approved paper:read permission') but no when-to-use-a-different-tool guidance. Nothing tells the agent when to prefer this over get_strategy or search_markets, so usage is only implied by the list scope.

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