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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, covering the operation's safety. The description adds 'bounded counts' and 'cover previews,' which suggests behavior beyond a plain list (e.g., limited results and preview fields), but it doesn't detail what 'bounded' means or what 'cover previews' entail. With annotations covering mutation concerns, a 3 is reasonable as it adds some context but not rich behavioral detail.

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 description is short and front-loaded with the verb, but it is not well-structured. It lacks detail on parameters and usage, making it concise at the cost of value. It reads like a fragment rather than a complete sentence, and the ambiguity in 'optional Series' undermines its efficiency.

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?

Given the tool has an output schema connectivity (there is an output schema, so return format is covered), but the description is was lacking for a list/read tool with 3 parameters. Without parameter semantics and sibling differentiation, the description is insufficient for an agent to correctly call it with the right workspace scope or understand pagination behavior, even with annotations present.

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%, and the description provides no parameter information. It doesn't explain 'limit', 'offset', or 'workspaceId' beyond what the schema names and types suggest. 'workspaceId' could be null, likely meaning 'all workspaces,' but the description leaves that unclear. For a tool with 3 parameters and zero schema descriptions, the description fails to compensate.

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 says 'List optional Series with bounded counts and cover previews,' which is unusually worded: 'optional Series' is vague (optional as in list is optional? or series have optional fields?), and it doesn't clarify what a Series is or how it differs from siblings like series_get, series_content, or series_apply. It names the verb 'List' and resource 'Series' but the qualifiers add confusion rather than clarity.

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 no guidance on when to use this tool versus alternatives. There are many list tools (media_list, characters_list, projects_list) and series-specific tools (series_get, series_content, series_apply) but no mention of when series_list is preferred. The 'bounded counts' hint implies pagination but doesn't explain when to use it.

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