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 without the description. The description adds genuine domain context (that a series has cadence, next wave time, and a metric/score rule) and clarifies the series-vs-study boundary, but says nothing about ordering, pagination, or result size.

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?

Two dense but well-ordered sentences: the entity definition comes first, the field list second, and the sibling boundary last. The '(ADR 0031)' citation is the only token that does not help an agent decide or call, so it is near-optimal rather than flawless.

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 carries the return-value burden and does so by enumerating the fields a series exposes, which is the right move for a list tool. It omits pagination and any note that results may be empty or workspace-scoped, which are minor gaps given the 100%-covered single optional parameter.

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?

There is a single optional parameter and schema description coverage is 100%, with the workspace slug and its token-dependent required/ignored rules documented in the schema itself. The description adds no parameter meaning beyond that, so the baseline 3 for high-coverage schemas applies.

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 the resource precisely as 'recurring research programs' and enumerates the fields they carry (name, cadence, enabled state, next wave time, wave count, metric/score rule), which lets an agent distinguish it from prism_series_create, prism_series_update, and prism_series_launch_wave. It never states the verb explicitly, so the listing action is inferred from the tool name rather than the text.

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 when-to-use statement, but the closing line 'Waves themselves are ordinary studies' implicitly routes the agent to the prism_studies_* tools when it wants wave content rather than series definitions. No exclusions, prerequisites, or direct sibling alternatives are named.

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