Server Quality Checklist

Tool Scores

• search_local_docsC
  2.7/5.0
  Behavior2/5

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

  No annotations are provided, and the description only states it searches without disclosing behavior like full-text search, exact match, pagination, or performance implications. The agent lacks information on what the tool actually does internally.

  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 a single sentence with no fluff. However, it is not front-loaded with the most critical information like parameter requirements or return type. Still, conciseness is adequate.

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

  Completeness1/5

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

  Given no output schema, no annotations, and only two parameters, the description is severely incomplete. It does not explain return values, result format, ranking, or edge cases, making it inadequate for an agent to use effectively.

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

  Parameters1/5

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

  Schema description coverage is 0%, and the description adds no meaning to the 'query' and 'maxResults' parameters. The agent only has the parameter names, which are insufficient for correct invocation.

  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 verb 'Search' and the resource 'locally extracted Salesforce documentation in the SQLite database'. It distinguishes the tool from siblings like 'read_local_document' which implies reading a specific document.

  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 does not provide when to use this tool versus alternatives. No explicit context or exclusion is given. Siblings like 'mass_extract_guide' or 'read_local_document' are not referenced for differentiation.

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

• export_local_documentsA
  3.6/5.0
  Behavior3/5

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

  With no annotations, the description carries full burden. It discloses the core action (concatenating and exporting to a local file) but omits important behaviors like overwrite policy, directory creation, handling of no matches, and file format specifics. Adequate but not thorough.

  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?

  Single sentence, no redundant words, front-loaded with key action. Every word earns its place.

  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 file export tool with 3 well-documented parameters, the description covers the main idea. Minor gaps (e.g., behavior on existing file) do not significantly impair understanding for most agents.

  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 coverage is 100%, with clear parameter descriptions. The tool description's phrase 'all matching' reinforces filtering but adds no new meaning beyond the schema. 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 clearly states the action ('export'), the resource ('offline documentation pages'), and the result ('concatenated into a single Markdown file on your local machine'). It distinguishes from siblings like read_local_document (single page) and mass_extract_guide (likely batch extraction without concatenation).

  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?

  No explicit guidance on when to use this tool instead of alternatives (e.g., mass_extract_guide, search_local_docs). The description does not mention context, prerequisites, or when to avoid using it.

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

• mass_extract_guideA
  4/5.0
  Behavior4/5

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

  No annotations are provided, so the description carries the full burden. It discloses that the tool stores contents in a local SQLite database for later searching, which is a key behavioral trait beyond the input schema. However, it does not address side effects like overwriting data, rate limits, or permissions.

  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 efficient sentences with no waste. Front-loaded with the primary verb 'Spiders'.

  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 spidering and bulk scraping tool without output schema, the description adequately explains the process and storage. It could be more complete by noting the relationship to sibling tools (e.g., search_local_docs for retrieval), but it is still sufficient.

  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 high (75%). The tool description does not add parameter-specific details beyond the schema; it only explains the overall process. For the undocumented 'category' parameter, neither schema nor description provides guidance, so the description does not compensate.

  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 specific verbs ('spiders', 'extracts', 'scrapes', 'stores') and clearly identifies the resource (Salesforce documentation page) and the bulk hierarchical action. It distinguishes from siblings like scrape_single_page (single page) and export/read/search local docs (different operations).

  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 bulk extraction from a root page but does not explicitly state when to use this tool versus alternatives (e.g., scrape_single_page for a single page). No when-not or exclusion criteria are provided.

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

• read_local_documentA
  4.2/5.0
  Behavior4/5

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

  The description indicates a read-only operation ('Read the full markdown content') with no side effects. With no annotations provided, it carries the full burden and does so adequately, though it could mention error handling (e.g., missing URL) or output format more explicitly.

  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?

  A single sentence conveys the purpose clearly without any unnecessary words or repetition. It is front-loaded and efficient.

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

  Completeness3/5

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

  While the tool is simple, the description does not explicitly state that the return value is the markdown content as a string, nor what happens if the URL is not found. Given no output schema, this information would help the agent understand the result format.

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

  Parameters5/5

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

  The input schema has 100% description coverage. The parameter description adds valuable context by specifying that the URL should be obtained from search_local_docs or mass_extract_guide, which clarifies the source beyond the schema's minimal description.

  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 reads markdown content of a Salesforce documentation page from the local SQLite database. It distinguishes itself from siblings like export_local_documents, mass_extract_guide, scrape_single_page, and search_local_docs by specifying the action (read) and the source (already extracted).

  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 after extraction by stating 'already been extracted,' and the parameter description hints at obtaining URLs from search or mass_extract. However, it lacks explicit guidance on when to use this tool versus alternatives, and no when-not-to-use information is provided.

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

• scrape_single_pageA
  4.2/5.0
  Behavior3/5

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

  No annotations are provided, so the description carries full burden. It states the tool scrapes a page and returns markdown, but does not disclose error handling, rate limits, or authentication requirements. This is adequate but lacks richness.

  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 sentences cover the function and crucial usage guidance. No filler; every word earns its place.

  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?

  Given the tool simplicity (2 params, no nested objects, no output schema), the description covers the main usage. It could mention the optional 'category' parameter or expected markdown structure, but overall it is sufficient.

  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 coverage is 0%; the description adds meaning to 'url' by specifying it must be a Salesforce documentation URL and advising how to find it. However, 'category' is entirely undocumented, leaving a gap.

  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 that the tool scrapes a single Salesforce documentation page and returns markdown. It specifies the resource (Salesforce docs) and the output format, distinguishing it from siblings which deal with local documents.

  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?

  Explicitly instructs the agent to use a web search tool if the exact URL is unknown, providing specific search queries. This gives clear guidance on when to use this tool versus search tools.

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