get_new_series

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

The readOnlyHint annotation indicates a safe read operation, but the description adds no additional behavioral context beyond 'list'. It does not disclose pagination behavior, filtering semantics, or what 'newly added' means precisely. Since the annotation already covers safety, the low bar for transparency is not met with any extra context.

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 extremely short, but this is under-specification rather than effective conciseness. One vague sentence fails to convey essential information about parameters, usage, or behavior, making it less useful than a longer but sufficiently detailed description.

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?

While the presence of an output schema covers return values, the description lacks critical context for a 7-parameter tool. It does not explain pagination, sorting, or the meaning of optional filters like oneshot and deleted, leaving the agent to guess or make incorrect assumptions.

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 0% schema description coverage, the description was expected to compensate for the 7 parameters, but it does not mention any of them. Parameter names like page, size, and sort are somewhat self-explanatory, but 'deleted', 'oneshot', and 'library_id' remain ambiguous without further explanation.

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 'List newly added series' uses a specific verb and resource, clearly indicating the tool returns a list of series that are new. However, it does not differentiate from sibling tools like get_latest_series or get_updated_series, which may overlap in meaning.

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 guidance on when to use this tool versus alternatives. The description does not mention use cases, exclusions, or that get_latest_series might be more appropriate for certain scenarios.

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