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

With no annotations provided, the description carries full responsibility for disclosing behavioral traits. It mentions data categories but does not describe performance implications (e.g., slower than individual endpoints), data freshness, error handling for partial failures, or the exact structure of the output. This is a significant gap for a aggregator tool.

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, front-loaded sentence that efficiently communicates the tool's purpose and scope. Every word adds value, and there is no redundant or extraneous content.

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 the tool's complexity (aggregating five data domains) and the absence of an output schema or annotations, the description provides only a high-level enumeration. It tells the user what areas are covered but not the specific metrics, return format, or usage caveats. This is minimally adequate but leaves gaps for a complex dashboard.

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?

The tool has zero parameters, so the description need not explain parameter-specific behavior. Baseline for 0-param tools is 4, and the description's enumeration of data areas gives some idea of what the dashboard covers, though it doesn't need to add more.

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's function as a comprehensive ECB dashboard covering rates, FX, inflation, economy, and yields in a single call. It distinguishes itself from sibling tools that focus on individual areas (e.g., ecb_rates, ecb_fx) by explicitly being the 'full' aggregate version.

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 phrase 'in one call' implies this is the go-to tool when a user wants comprehensive ECB data without making multiple separate calls. It provides clear context on its broad scope, though it doesn't explicitly mention alternatives or exclusion scenarios.

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