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 fully covered by structured data. The description adds meaningful context beyond that: it explains what the returned records represent (recurring programs with cadence and score rules) and clarifies the domain boundary that waves are ordinary studies. It does not cover pagination, result volume, or whether series are workspace-scoped at all.

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?

The content is compressed into a single sentence with an enumerated field list, front-loading the resource definition. The ADR 0031 citation is arguably noise for an invoking agent, and the sentence runs long, but there is no padding or repetition.

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 usefully enumerates the returned fields, which is the main thing lacking elsewhere. However, for a list tool it omits pagination, ordering, and result-size behavior, and never states how many series are typically returned or what an empty result means.

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 100% and there is only one optional parameter (workspace), whose semantics — default-workspace behavior and API-key handling — are fully documented in the schema. The description adds no further meaning about the parameter, so the baseline of 3 is appropriate.

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?

The description identifies a specific resource — recurring research programs (series) — and enumerates the fields it surfaces (name, cadence, enabled state, next wave time, wave count, metric/score rule). Combined with the title 'List research series' and the sibling names prism_series_create/update/launch_wave, an agent can infer this is the read/list counterpart. It never states the verb 'list' in the description text itself and does not explicitly contrast with prism_series_get-style siblings, so it falls 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?

There is no explicit statement of when to call this versus alternatives, and no prerequisites or exclusions. The closing note 'Waves themselves are ordinary studies' is an implied routing hint (use prism_studies_* for waves rather than this tool), but it is a disambiguation aside rather than usable when-to-use guidance.

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