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 covered. The description adds useful context that results are withheld for stale/unavailable/unverified inputs, but does not explain what 'source receipts' or 'native units' mean in output terms.

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?

Two sentences of moderate length, front-loaded with the action. However, the heavy noun-stacking ('trailing-window missingness, native units and source receipts') reduces readability rather than stating points cleanly.

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?

With 4 undocumented parameters, no output schema, and no annotations describing return behavior, the description leaves major gaps. An agent cannot infer what 'source receipts' contains or how window affects results, so it is insufficient for correct invocation.

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% across 4 parameters (dataset, series, entity, window), so the description must compensate. It mentions 'one exact entity' and 'latest captured series' and 'trailing-window', offering only vague hints about entity, series, and window semantics, leaving dataset entirely 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 an action (analyze) and a resource (series), but phrases it in dense jargon ('adjacent change, trailing-window missingness, native units and source receipts') that obscures what the tool actually returns. It is difficult to distinguish from siblings like research_analysis and research_series based on this text alone.

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 implies a single-entity scope ('one exact entity'), which is a light constraint, but provides no explicit guidance on when to use this tool versus research_analysis or research_series. No alternatives or exclusion conditions are named.

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