Server Quality Checklist

Tool Scores

• smugmug_api_callB
  3.4/5.0
  Behavior2/5

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

  No annotations are provided, so the description alone must disclose behavioral traits. It mentions pre-authorized OAuth credentials but does not explain potential side effects of using methods like POST/DELETE, rate limits, error behavior, or that the tool can perform mutations depending on the method parameter. This is a significant transparency gap for a tool that can potentially alter data.

  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, efficient sentence that immediately conveys the core purpose. It contains no filler and is front-loaded with the key information (live API call).

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

  Completeness2/5

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

  With no output schema and no annotations, the description should explain what the tool returns or how the response is structured, but it does not. It also lacks any mention of possible errors, pagination, or how the response relates to the requested path. Given the tool's generic API-call nature, this is insufficient for an agent to fully understand invocation consequences.

  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 input schema has 100% description coverage, with each parameter (path, method, params) already explained. The tool description adds no additional meaning beyond the schema, so the baseline of 3 is appropriate. It does not clarify parameter formatting or provide examples beyond what the schema already shows.

  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 calls the live SmugMug API with pre-authorized credentials, which is a specific verb and resource. It distinguishes itself from the sibling documentation tools (search_smugmug_docs, fetch_smugmug_doc) by focusing on live API interaction rather than doc retrieval.

  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 phrase 'live SmugMug API' implies it should be used when making actual API requests rather than consulting docs, and the sibling names help infer that. However, there is no explicit statement about when to use this tool vs the documentation tools, nor any exclusions or prerequisite conditions.

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

• fetch_smugmug_docA
  3.5/5.0
  Behavior2/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 only says 'fetch content,' which is straightforward, but it does not disclose what the returned content looks like, error behavior, or any rate limits. It lacks context beyond the basic action, leaving the agent uncertain about the output format or failure modes.

  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 with no redundant words. It is front-loaded with the verb and resource, making it efficient and easy to scan.

  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?

  The tool is simple with one parameter and no output schema, so the description does not need to explain return values fully. However, it does not mention what the 'content' is (e.g., raw HTML, text) or the expected behavior for invalid paths. For a read-only fetch tool, it is minimally complete but has clear 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?

  Schema coverage is 100% for the single parameter 'input', which has a clear description ('A full URL or a docs path such as tutorial/api-key.html'). The tool description essentially repeats this information, adding no new semantic value. The baseline of 3 applies.

  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's function: 'Fetch content from a SmugMug docs page or a known docs path.' It uses a specific verb (fetch) and a specific resource (SmugMug docs page/path), and it is distinct from sibling tools like search_smugmug_docs and smugmug_api_call.

  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 (when you need to fetch docs content from a URL or path) but provides no explicit guidance on when to use this vs. search_smugmug_docs or smugmug_api_call. There are no exclusions or alternative suggestions, so it only meets the 'implied usage' level.

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

• search_smugmug_docsA
  3.9/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 the full burden. It states the action ('Search'), which implies a read-only operation, but does not disclose what the output looks like, whether it searches full text or just metadata, or any limits. For a simple search tool this is acceptable, but it leaves some behavioral details implicit.

  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 that clearly states the tool's purpose without unnecessary words. It earns its place by being concise and immediately informative.

  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?

  Given the tool's simplicity (one parameter, no output schema), the description is reasonably complete. However, it does not specify what the search returns (e.g., a list of document ID's, snippets), which could be important for an agent deciding how to proceed. The absence of any return-value guidance leaves a minor 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?

  The input schema has 100% description coverage for the single parameter 'query', providing examples like 'album, image, auth, or user'. The tool description itself adds no additional parameter meaning beyond what the schema already provides, so the baseline score of 3 applies.

  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 a specific verb ('Search') and identifies the resource ('the bundled SmugMug API documentation catalog'). It clearly distinguishes from sibling tools like fetch_smugmug_doc, which likely retrieves a specific document, and smugmug_api_call, which makes API calls. The purpose is unambiguous.

  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 implies the tool is for searching documentation, which provides context for when to use it (when the agent needs to locate docs). However, it does not explicitly mention when to avoid it or prefer an alternative like fetch_smugmug_doc. The sibling names offer hints, but the description itself lacks explicit exclusions or alternatives.

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