Server Quality Checklist

Tool Scores

• nfse_buscarA
  3.8/5.0
  Behavior3/5

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

  With no annotations provided, the description carries the full transparency burden. It discloses return fields (date, recipient, value, status, key) but does not mention permissions, pagination, ordering, or side effects. Adequate for a simple read operation but not comprehensive.

  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 a single sentence, efficient, and front-loaded with the verb and resource. It contains no wasted words and is easy to parse.

  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?

  For a simple two-parameter search tool without an output schema, the description adequately lists the return fields. It lacks details on pagination or ordering but is sufficient given the tool's simplicity.

  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% with both parameters clearly documented as date strings with format. The description itself adds no additional parameter semantics beyond the schema, so the baseline score of 3 is appropriate.

  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 uses the specific verb 'Busca' (search) and identifies the resource (NFSe) and the period filter, clearly distinguishing it from sibling tools like nfse_detalhes and nfse_pdf.

  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 for searching NFSe by date range, but does not explicitly state when to use this tool versus alternatives or provide exclusions. It is adequate but lacks explicit guidance.

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

• nfse_detalhesA
  4/5.0
  Behavior3/5

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

  With no annotations provided, the description must disclose side effects and context. It reveals a significant side effect: 'salva o XML localmente' (saves the XML locally). It also lists return data. However, it lacks deeper context such as authorization requirements, failure modes, or the format/path of the saved XML. Thus, it provides basic but not exhaustive transparency.

  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?

  Two short sentences that are entirely informative: first states the main purpose, second lists return data and the side effect. No filler or repetition.

  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 tool is simple with one parameter and no output schema. The description covers the main function, the specific return elements, and the local XML saving side effect. It lacks only minor details (e.g., where the XML is saved, whether it returns anything beyond a confirmation), but overall it is sufficiently complete for 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?

  Schema description coverage is 100%, as the 'chave' parameter already has a description ('Chave identificadora da NFSe'). The tool description redundantly mentions 'a partir de sua chave' but adds no new semantic detail about the key's format or constraints. Baseline 3 is appropriate.

  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 uses the specific verb 'Obtém' (gets) with the resource 'detalhes completos de uma NFSe específica' and specifies the input source 'a partir de sua chave'. It also lists the returned data categories (cabeçalho, emitente, valores, DPS), clearly distinguishing it from sibling tools like nfse_buscar (search) and nfse_pdf (PDF generation).

  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 clearly indicates when to use the tool: when you have a specific NFSe key and need complete details. It provides context without explicitly naming alternatives or exclusions, but the sibling tools imply differentiation. Given the clear context, it earns a 4.

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

• nfse_pdfA
  4/5.0
  Behavior4/5

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

  With no annotations, the description carries the full burden. It discloses the key behavioral trait that the PDF is saved locally and returns the file path ('Retorna o caminho do arquivo PDF salvo localmente'). It stops short of disclosing error handling, file overwrite behavior, or permission requirements, but the primary side effect is clearly stated.

  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 a single, front-loaded sentence starting with the verb 'Baixa'. It provides essential information with 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?

  For a simple one-parameter tool with no output schema and no annotations, the description sufficiently explains what it does and what it returns. It could mention that the key must belong to an existing NFSe (obtained via sibling tools), but this is implied by the purpose and not a major gap.

  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% (the only parameter 'chave' is described as 'Chave identificadora da NFSe'). The description adds no extra meaning beyond restating that the download is 'a partir de sua chave'. Baseline of 3 applies as the schema already documents the parameter.

  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 downloads the PDF (DANFSe) of a specific NFSe using its key, with a specific verb ('Baixa') and resource. This distinguishes it from siblings 'nfse_buscar' (search) and 'nfse_detalhes' (details).

  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 via the action (download PDF from a given key) but does not explicitly state when to use it versus siblings or any exclusions. There is no guidance like 'use nfse_buscar to find the key first' or 'this is the only tool that returns a local file path.'

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