series

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It explains a non-obvious update mode (fetch by ids versus discover by quantity), but it says nothing about whether add/update mutate data, permission requirements, validation, or what search/get return.

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 two short sentences, front-loaded with the resource and action list, with no filler. Its terseness is a completeness issue rather than a conciseness issue.

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?

For a seven-parameter, four-action tool with no annotations and no schema parameter descriptions, the description covers only one branch of one action. The output schema may cover return values, but input semantics and most action behavior remain largely undocumented.

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%, so the description must compensate for seven undocumented parameters. It only gives meaning to ids and quantity in the update-specific note, leaving id, text, as_of, entry, and the action values unexplained.

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 the resource ('Stored series') and enumerates the four actions, so an agent can identify this as the series-management tool rather than corpus, scenario, run, model, portfolio, or jobs. It is clear at the resource/action level, though it does not explain what search, get, or add actually do.

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 does not say when to use search versus get versus add versus update, nor when to prefer this tool over its siblings. The only conditional guidance is the internal update behavior involving ids and quantity.

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