get_pa_time_series

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

Annotations already declare readOnlyHint=true, so the read-only nature is established. The description adds the concept of 'historical time-series' which is useful context, but does not disclose output format, pagination, or any operational constraints beyond what annotations and schema already provide.

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?

A single, concise sentence that front-loads the verb and resource. No wasted words; the statement earns its place by conveying both the action and the purpose.

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 simple parameters, annotations, and no output schema, the description is adequate for selection and invocation. It could be improved by specifying the output shape or units, but the provided information is sufficient for basic use cases.

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 100%, so each parameter (indicator_sys_id, start_date, end_date, limit) is already described. The description adds no additional meaning about parameter relationships or format, so the baseline of 3 applies.

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 clearly states the action ('Get'), the resource ('historical time-series data for a PA indicator'), and the purpose ('to identify trends'). It distinguishes from sibling tools like get_pa_indicator (which likely returns indicator metadata) and list_pa_indicators (which lists indicators).

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 usage for trend analysis via 'to identify trends', but does not explicitly compare to alternatives such as trend_query or visualize_trend. It provides no exclusions or when-not-to-use guidance, so it only partially guides tool selection.

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