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

Annotations already declare readOnlyHint=true, idempotentHint=true, non-destructive, closed-world, so the safety profile is covered. The description adds nothing beyond a pointer to describe_operation, and does not disclose pagination, default time range, or response shape for what is presumably a large historical series.

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?

The only substantive sentence is the endpoint path, and it is duplicated verbatim, wasting half the text. The operation-ID/describe_operation line is boilerplate.

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 no output schema, 0% parameter coverage, and a nested free-form query object, the description should explain expected query fields and return shape. It does neither, so an agent cannot call this correctly without a second describe_operation round-trip.

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% and the two parameters (a free-form 'query' object and an empty 'params' object) are entirely undocumented. The description only says describe_operation provides native request schemas, delegating the work rather than explaining that query params (e.g. date range) belong in 'query' and 'params' is empty.

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 is essentially the endpoint path repeated, which does name a resource (prime-rate history) and verb (GET), so an agent can infer it returns historical prime rate data. However, it offers no differentiation from close siblings like get_economic_data_prime_rate_current, get_economic_data_prime_rate_calculate, or get_economic_data_cpi_history, leaving scope ambiguous.

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?

No guidance on when to use this versus the current-rate or calculate variants, no mention of what window or granularity the history covers, and no preconditions. The agent must guess from the tool name alone.

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