Server Quality Checklist

Tool Scores

• get_random_photosA
  4/5.0
  Behavior3/5

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

  No annotations provided, so description bears full burden. Mentions random nature and optional filters but lacks details on side effects, rate limits, or auth requirements. Adequate for a simple read tool but could be more informative.

  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?

  Three sentences, front-loaded with core function. Every sentence adds value: purpose, usage guidance, and differentiation. No wasted words.

  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?

  Output schema exists, so return values are covered. Description explains randomness, optional keyword, and suitable use cases. Lacks details on error handling or count limits, but overall sufficient for intended use.

  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%, so baseline is 3. Description only adds that query is a keyword filter; other parameters (count, orientation, content_filter) are left to schema. No additional meaningful context beyond schema.

  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?

  Description clearly states verb 'Get random photos' and resource 'from Unsplash', with optional keyword filter. Distinguishes from sibling 'search_photos' by emphasizing variety and lack of specific intent.

  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?

  Explicitly suggests use cases (hero images, backgrounds) and when to use (variety, no specific image). Implicitly contrasts with search_photos for specific needs, though no direct 'do not use when' clause.

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

• search_photosA
  4/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 adds one behavioral requirement: 'full attribution data that MUST be displayed.' However, it does not disclose other behaviors such as rate limits, pagination behavior, or error handling. The attribution info is useful but insufficient for full 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?

  The description is extremely concise: two sentences, no wasted words. The first sentence states the purpose, and the second provides usage context and a crucial requirement. It is front-loaded and efficient.

  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 that an output schema exists, the description does not need to explain return values. It covers the main purpose and a key usage requirement (attribution). However, with 7 parameters and no annotations, it could briefly mention pagination or sorting behavior (already in schema but not highlighted). Still, it is reasonably complete for a search 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 documents all 7 parameters thoroughly. The description adds no additional parameter semantics beyond what is in the schema. 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 clearly states 'Search for photos on Unsplash by keyword,' which is a specific verb+resource. It is easily distinguishable from sibling tools like get_random_photos (random selection) and track_download (tracking), even though no explicit differentiation is provided.

  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 clear context: 'Use this tool when you need to find photos for a specific topic or theme.' It also mentions the attribution requirement. However, it does not explicitly state when not to use this tool or how it compares to siblings, which would improve guidance.

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

• track_downloadA
  4/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 burden of behavioral disclosure. It explains that the tool is mandatory for API compliance and tracks usage statistics, but does not detail side effects (e.g., whether it mutates state), rate limits, authorization needs, or return behavior. The requirement 'MUST call' is clear, but additional context on what exactly happens when called (e.g., API call logging) is lacking.

  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 highly concise with four sentences, each adding distinct value: requirement statement, when to call, why required, and when not to call. No redundancies or unnecessary details.

  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 is simple (1 required parameter, output schema present), the description adequately covers usage context, necessity, and timing. It does not explain return values, but the presence of an output schema mitigates that need. Minor gap: no mention of error handling or idempotency, but overall complete for the tool's purpose.

  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%, so the baseline is 3. The description adds no additional meaning to the 'photo_id' parameter beyond what the schema already provides ('The photo ID from a previous search_photos or get_random_photos result'). The description merely references this parameter context without enriching it.

  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 purpose: tracking photo downloads as required by Unsplash API guidelines. It specifies the action ('track a photo download'), the resource (photo), and distinguishes from sibling tools like search_photos and get_random_photos by noting when to call it ('AFTER the user confirms they want to download/use the image') and when not to ('not when just displaying search results').

  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 provides usage context: it must be called when a user downloads or saves a photo, and is required by Unsplash guidelines. It also states when NOT to use it ('not when just displaying search results'). However, it does not explicitly name alternative tools or explain why search tools are inappropriate for tracking, missing an opportunity for full sibling differentiation.

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