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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is fully covered. The description contributes only the underlying REST route, which adds minor context but says nothing about authentication, rate limits, or error behavior.

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?

It is short and front-loaded, but the opening line duplicates the title verbatim, so half the content carries zero incremental information. Concision here comes from under-specification rather than tight writing.

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?

An output schema exists, so return shape needn't be described, but the core semantic question — what 'length' measures for a series under a given index — is left unanswered. For a tool in a dense family of near-identically named get_series* siblings, more disambiguation is required.

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 reported at 0% and the description says nothing about the 'series' or 'index' parameters. The embedded $defs do supply an enum and examples for Index, but the description itself never confirms that 'series' is a name from list_series or explains the aggregation dimension's role in the length calculation.

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?

States the verb 'get' and the resource 'series data length', but the first line is essentially a restatement of the title with no elaboration on what 'length' means (number of data points? size of response array?). It does not distinguish itself from the very similar sibling get_series_count, leaving the agent unable to tell the two apart.

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 versus get_series, get_series_count, get_series_latest, or get_series_bulk. The most important disambiguation — this tool versus get_series_count — is completely unaddressed.

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