get_historical_data

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

With no annotations, the description must convey behavioral traits. It specifies JSON format and granularity options but does not disclose read-only nature explicitly, auth requirements, or error handling. The verb 'Retrieve' hints at idempotency but lacks depth.

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 that are front-loaded: the first states core function, the second elaborates use cases. No superfluous text, every sentence is purposeful.

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?

Given 2 parameters and no output schema, the description covers the retrieval purpose but lacks detail on return structure (beyond JSON) and does not fully differentiate from sibling performance tools. Adequate but not complete.

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 coverage is 100% with parameter descriptions. The description adds 'JSON format' and mentions 'trends, transaction reports, time-series metrics', but the schema already details granularity options. The added value is moderate.

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 tool retrieves historical performance data for a specific date with configurable granularity, using specific verbs like 'Retrieve' and 'Analyze'. It distinguishes from siblings like get_issues and get_performance_summary by focusing on historical data with granularity options.

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 analyzing historical trends but does not explicitly state when to use this tool versus alternatives like get_performance_summary. No exclusions or when-not guidance is provided.

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