bde_serie

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

No annotations are provided, so the description must fully disclose behavior. It states the tool returns the 'latest value', but does not explain behavior for invalid series codes, multiple series (comma-separated), or any side effects. The lack of behavioral detail is a significant gap for a tool without 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?

The description is extremely concise, consisting of two sentences that efficiently convey the purpose and context. Every sentence adds value without redundancy.

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 simplicity (one parameter) and the presence of an output schema (so return values need not be described), the description is reasonably complete. However, it lacks information on error handling, authentication, or limitations, which would be expected given the absence of annotations.

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 100%, so baseline is 3. The description adds context about the types of series available (Euribor, IPC, etc.), supplementing the schema's examples. However, it does not add much beyond what the schema already provides, so the baseline score is appropriate.

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 purpose: obtaining the latest value of financial series from the Bank of Spain. It specifies the resource (financial series from BDE) and the action (obtain latest value), and distinguishes it from siblings like 'bde_series_destacades' which likely provides predefined highlighted series.

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 provides a high-level use case ('Per contextualitzar investigacions amb dades macroeconòmiques'), but does not offer explicit guidance on when to use this tool versus alternatives like 'bde_series_destacades' or other data tools. No exclusions or prerequisites are mentioned.

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