Server Quality Checklist

Tool Scores

• bcentral_serie_infoA
  4.1/5.0
  Behavior3/5

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

  Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds context that it returns metadata fields rather than data, but does not disclose additional behavioral traits like error handling, rate limits, or pagination. With annotations covering the main concerns, a score of 3 is appropriate.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is two sentences, front-loaded with the core purpose and immediately followed by a concrete use case. Every word earns its place with no fluff or redundancy.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness5/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Given the simple nature of the tool (2 parameters, 1 required), the presence of an output schema, and strong annotations, the description is complete. It conveys the tool's official nature, the metadata fields returned, and the recommended usage context, leaving no critical gaps.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  The schema provides a solid description for 'timeseries' including comma-separated codes and a max of 30, with an example. The 'lang' parameter has an enum (es/en) that is self-explanatory. The description adds only that it handles one or more series, which is already implied by the schema, so it does not significantly enhance parameter understanding.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description clearly states the tool returns official metadata (description, frequency, unit) for one or more BDE series. It explicitly distinguishes this from data retrieval by noting it's useful to verify a code exists before requesting data, which differentiates it from the sibling tools bcentral_serie_datos and bcentral_series_populares.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines4/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description explicitly says to use this tool before requesting data to verify a code exists and what it represents. It gives clear contextual guidance but does not explicitly name alternative tools or state when not to use it, though the 'antes de pedir datos' phrase implies the contrast with data-fetching tools.

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

• bcentral_serie_datosA
  4.2/5.0
  Behavior4/5

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

  Annotations already declare readOnlyHint and destructiveHint false, so the safety profile is covered. The description adds valuable behavioral context: authentication via BCENTRAL_API_KEY and a per-call limit of 30 series. This goes beyond the minimal annotation information, though it doesn't cover other potential aspects like rate limits or error behavior.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is two sentences, both informative and waste-free. It front-loads the core purpose, then adds necessary constraints. No filler or redundancy.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness4/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  With an output schema and complete parameter descriptions, the description covers essential context: purpose, authentication requirement, and series limit. The sibling tools are known, and the description implicitly differentiates. Slight gaps remain around error conditions or response format, but these are partially covered by the output schema, so the description is effectively complete for a data-fetching tool.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema description coverage is 100%, so the schema already explains each parameter in detail. The description does not add significant extra meaning beyond what the schema provides; it reiterates the period range concept but lacks new semantic details. The baseline of 3 applies when schema does the heavy lifting, and the description adds only marginal value here.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description clearly states it returns observaciones (observations) of economic series from the Central Bank database over a period range. It names the specific database (BDE/SIETE) and the resource type, making it distinct from sibling tools like bcentral_series_populares or bcentral_serie_info, which are for listing popular series or retrieving metadata.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines4/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description provides important context on prerequisites (BCENTRAL_API_KEY) and constraints (max 30 series per call). It does not explicitly say when to use this tool over siblings, but the context is clear enough for an agent to infer this is for fetching data, not for metadata or popular series lists.

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

• bcentral_series_popularesA
  4.7/5.0
  Behavior4/5

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

  The description adds behavioral context beyond the readOnlyHint annotation by noting it is 'local (sin red ni clave)'—meaning no network or credentials are required, and it runs locally. It also implies the catalog is a static list rather than a live query. There is no contradiction with annotations.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is two sentences with high information density: it states the purpose, gives examples, and provides actionable guidance in the second sentence. No fluff or redundancy.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness5/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  For a no-parameter tool with an output schema, the description fully covers what the agent needs to know: what the catalog is, what it contains, where to find the full catalog, and how to verify codes. The output schema handles return format, and annotations handle safety, so nothing is missing.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters4/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  The tool has zero parameters, so the baseline is 4. The description adds context by enumerating the types of series included (inflation, rates, GDP, unemployment), which helps the agent understand the scope of the catalog, even though no parameter details are needed.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description clearly identifies the tool as a 'Catálogo local de las series más usadas de la BDE' (local catalog of the most used BDE series) and lists concrete examples (UF, UTM, IPC, TPM, exchange rate, IMACEC, GDP, unemployment). It distinguishes itself from siblings by emphasizing the 'local' and 'popular' nature, and by pointing to the full catalog elsewhere.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines5/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description explicitly states when to use the tool (for a quick local list of popular series without network/key) and when to use alternatives: the complete catalog is available at si3.bcentral.cl/Siete, and code verification should be done with bcentral_serie_info. This provides clear contrasts with sibling tools and external resources.

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