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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds useful behavior around null seriesId and sourceId filtering, but does not disclose pagination, result shape, or how workspaceId influences the list; the output schema mitigates some of this.

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 tight sentences, with the primary purpose front-loaded and no filler. The null-seriesId behavior and sourceId filter are high-value details expressed economically.

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?

The description is adequate for the core list-and-filter scenario, and the output schema plus annotations supply return and safety context. Still, with seven parameters all listed as required and no explanation of workspaceId or search semantics, an agent may struggle to construct a fully correct request without additional inference.

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?

With schema description coverage at 0%, the description must compensate, but it only clarifies seriesId, sourceId, and the kind distinction. It leaves workspaceId, search, limit, and offset semantics unexplained, and workspaceId is a required parameter with nullable/default ambiguity that an agent may not resolve from the schema alone.

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 names a specific verb and resource combination ('List sources or projects in a Series') and clarifies the key distinction between in-series and standalone content. This differentiates it from series_list and series_get, which focus on the series objects themselves rather than their contents.

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?

The description gives clear operative context: 'Null seriesId lists standalone content' tells the agent when to pass a null seriesId, and 'sourceId filters projects by clip origin' explains an important filtering scenario. It does not explicitly name alternative tools or exclusions, but the usage context is sufficient for a listing operation.

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