Buscar índices de precios de comercio exterior del BCE

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds one useful trait — 'Returns links' — which tells the agent the payload is references rather than data, but no further behavioral context (auth, pagination) is given.

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?

Three short sentences, front-loaded with the resource scope and closing with the return shape. No filler, though it could be slightly tighter.

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?

An output schema exists so return values needn't be explained, and the annotations carry the safety profile. The description supplies scope, granularity-vs-BCEData, and the link-returning nature, leaving little an agent would still need before calling.

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%, so both the query matching behavior (label, page title, page id, accent-insensitive) and the format enum are already fully documented in the schema. The description's mention of categories/products is contextual rather than parameter-specific, so baseline 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?

States a specific verb and resource — BCE foreign-trade price-index files — and enumerates concrete coverage (import use category, export product: oil, shrimp, banana, cacao). It also differentiates itself from the BCEData aggregates, though it doesn't name a specific sibling search tool.

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?

'BCEData only has the aggregates' implies this tool is for the disaggregated files, giving an implicit routing cue, but there is no explicit when-to-use/when-not guidance nor a named alternative among the many search_bce_* siblings.

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