Server Quality Checklist

Tool Scores

• ml_detalhe_anuncioA
  3.7/5.0
  Behavior4/5

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

  Annotations indicate readOnlyHint, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds value by specifying the return format (JSON with common fields, description, images, seller, and error handling), which is beyond the annotations. It does not mention rate limits or authentication, but for a read-only tool this is acceptable.

  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 extremely concise: two sentences for the main purpose, plus structured 'Args' and 'Returns' sections. Every part adds value without 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 simple tool (1 param, no nested objects) with an output schema available, the description covers the purpose, input parameter, and return format (including error handling). It is complete given the context.

  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 description restates the 'url' parameter and its purpose, which is already documented in the input schema. With schema description coverage at 0% (implying schema lacks descriptions, though the schema actually has one), the description adds minimal new meaning. Baseline 3 is appropriate.

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

  Purpose4/5

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

  The description clearly states it retrieves details of a Mercado Livre listing from a URL, using the verb 'Obtém' (gets) and specifying the resource and platform. It is implicitly differentiated from siblings like ml_buscar_anuncios (search) and olx_detalhe_anuncio (OLX platform).

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

  Usage Guidelines2/5

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

  The description provides no guidance on when to use this tool versus alternatives, such as when to search vs. get details, or any prerequisites (e.g., valid URL format). It only states the action.

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

• olx_detalhe_anuncioA
  3.9/5.0
  Behavior4/5

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

  The description reveals that the description field has HTML removed and lists all returned fields, adding detail beyond the readOnly and idempotent annotations. No contradictions are present.

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

  Conciseness4/5

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

  The description is well-structured with separate Args and Returns sections, and the purpose is front-loaded. It is not overly verbose for the detail provided.

  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?

  The description comprehensively covers input and output fields, and annotations are present. Missing error handling details but adequate for selection and invocation.

  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 'url' parameter's description in the tool text ('URL completa do anúncio na OLX') adds minimal meaning beyond the schema's own description (which includes an example). Given the context signal of 0% schema coverage, this is adequate but not exceptional.

  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 retrieves complete details of a specific OLX listing from its URL. This explicitly differentiates it from sibling tools that perform searches or work with Mercado Livre.

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

  Usage Guidelines3/5

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

  The description implies usage with a URL but does not explicitly guide when to use this tool versus alternatives like 'olx_buscar_anuncios' for searches. No exclusions or when-not-to-use are provided.

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

• olx_buscar_anunciosA
  4.2/5.0
  Behavior4/5

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

  Annotations already declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint. The description adds details on pagination limits (1-50), ordering options, and price range, but does not mention rate limits or authentication. 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.

  Conciseness4/5

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

  The description is well-structured with a clear purpose statement, followed by parameter and return lists. It is informative but slightly verbose; could be more concise without losing clarity.

  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 complexity of the tool (multiple filters, pagination, ordering), the description covers all essential aspects, including the return format. It is fully adequate for an agent to use correctly.

  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 description adds value beyond the input schema by providing example values for each parameter (e.g., 'sp', 'notebook', 500). The schema already has descriptions for each property, but the description consolidates and contextualizes them effectively.

  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 searches public ads on OLX Brazil with various filters and returns a paginated list. It distinguishes from sibling tools (ml_buscar_anuncios, ml_detalhe_anuncio, olx_detalhe_anuncio) by specifying the platform and action.

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

  Usage Guidelines3/5

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

  The description does not explicitly compare with sibling tools or state when to use this tool vs alternatives. However, the platform-specific name and description imply it's for OLX searches, providing implicit guidance.

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

• ml_buscar_anunciosA
  4.3/5.0
  Behavior4/5

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

  Annotations indicate read-only, idempotent, non-destructive. The description adds behavioral context beyond annotations, warning about heuristic filters (estado, condicao) and their limitations (best-effort, frequent empty results). This helps the agent understand reliability.

  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 concise with a structured Args/Returns format. Every sentence adds value, including warnings. No fluff.

  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 tool's complexity (multiple parameters, heuristics, output schema), the description covers all necessary aspects: purpose, parameters, return format, and caveats. Annotations cover safety. No gaps.

  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?

  Schema description coverage is 0%, so the description fully explains each parameter: query required, price range, state (with warning), condition, and page. It adds meaning about post-scraping heuristics and unit (reais).

  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 searches for listings on Mercado Livre Brazil, a specific verb+resource. It distinguishes from siblings like ml_detalhe_anuncio (details) and olx_buscar_anuncios (different platform).

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

  Usage Guidelines3/5

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

  The description does not explicitly state when to use this tool versus alternatives. While sibling names suggest context, there is no explicit guidance on when to prefer this tool or exclusions.

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