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

Annotations already declare readOnlyHint, idempotentHint, and a closed-world profile, so the safety contract is covered elsewhere. The description adds nothing beyond that: no indication of what the response contains, freshness, or scope. It does not contradict the annotations.

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, but the first sentence is duplicated verbatim and the operation ID adds no decision value. The opportunity cost is high: the space that could have described purpose is spent on repetition.

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 and 0% parameter coverage, the description carries the burden of explaining behavior and inputs, and it delivers neither. Only the cross-reference to describe_operation keeps it from being entirely uninformative.

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 are untyped generic 'query' and 'params' objects with additionalProperties free-form. The description supplies no parameter meaning at all, leaving an agent unable to know what to send.

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 only repeats the endpoint path 'GET /api/economic-data/current' twice, which is a tautological restatement of the name rather than an explanation of purpose. It gives no hint of what 'current economic data' contains or how it differs from siblings like get_economic_data_cpi_current or get_economic_data_prime_rate_current.

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 only actionable guidance is a pointer to describe_operation for request schemas, which is a workflow hint rather than a when-to-use statement. There is no mention of when to pick this endpoint over the CPI-current or prime-rate-current siblings, nor any prerequisites.

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