get_changed_series_list

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

No annotations, so description fully carries the burden. Discloses SSL verification disabled, lists exception types, and mandates citation of VectorId. This goes beyond basic read-op disclosure.

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?

Starts with the main purpose, then adds relevant details. A bit verbose with the exception list, but all sentences contribute to understanding. Well-organized.

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 one-param tool with no output schema, description covers return type, fields, and exceptions. Could include an example, but overall complete enough.

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 only has a bare string 'date' with 0% coverage. Description adds the required format (YYYY-MM-DD) and endpoint path, making the parameter's meaning clear.

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?

Clearly states it gets the list of series updated on a date, with specific fields (vectorId, productId, coordinate, releaseTime) and the endpoint. Distinguishes from siblings like get_changed_cube_list by focusing on series.

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?

Provides clear context: use to get a list of changed series for a specific date. No explicit alternatives or exclusions, but the scope is well-defined and the endpoint is given.

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