Server Quality Checklist

Tool Scores

• get_trendingC
  2.9/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 of behavioral disclosure. It states the tool 'Get[s] trending and popular skills,' implying a read-only operation, but doesn't address other behavioral aspects such as authentication requirements, rate limits, error handling, or response format. For a tool with no annotation coverage, this is a significant gap in 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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded and wastes no space, making it highly concise and well-structured for quick understanding.

  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?

  Given the complexity of a tool with three parameters and no annotations or output schema, the description is incomplete. It lacks details on behavioral traits, usage guidelines, and expected outputs, which are crucial for effective tool invocation. The high schema coverage doesn't compensate for these gaps in contextual information.

  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 clear documentation for all three parameters (period, platform, limit), including enum values and defaults. The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline score of 3 for adequate coverage without extra value.

  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 the tool's purpose: 'Get trending and popular skills on agentskill.sh.' It specifies the verb 'Get' and the resource 'trending and popular skills,' making the action and target explicit. However, it doesn't differentiate this from sibling tools like 'get_skill' or 'search_skills,' which might also retrieve skill-related data, so it doesn't reach the highest score.

  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. It doesn't mention sibling tools like 'get_skill' or 'search_skills,' nor does it specify contexts or exclusions for usage. This lack of comparative information leaves the agent without clear direction for tool selection.

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

• install_skillC
  2.9/5.0
  Behavior2/5

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

  With no annotations provided, the description carries full burden. It mentions downloading files, which implies network activity and local file system changes, but doesn't disclose permissions needed, whether it overwrites existing skills, error handling, or rate limits. More behavioral context is needed for a mutation tool.

  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?

  Two concise sentences with no wasted words, front-loading the main action. It could be slightly improved by integrating parameter hints, but it's efficiently structured.

  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?

  For a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on success/failure outcomes, side effects, and error conditions. Given the complexity of installing skills, more context is needed to guide the agent effectively.

  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 both parameters. The description adds no additional meaning about parameters beyond what the schema provides, such as format examples for 'slug' or default behavior for 'targetDir'. Baseline 3 is appropriate when schema does the heavy lifting.

  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 the action ('Install a skill') and resource ('from agentskill.sh to the local skills directory'), including downloading specific files. It distinguishes from siblings like get_skill (retrieval) and search_skills (searching), but could be more explicit about the difference from get_trending.

  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 versus alternatives like get_skill or search_skills. The description implies installation from a specific source (agentskill.sh), but doesn't state prerequisites, when not to use it, or compare with sibling tools.

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

• search_skillsC
  2.9/5.0
  Behavior2/5

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

  With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the return format ('Returns matching skills with name, description, rating, and install count'), which is helpful, but lacks critical details like pagination behavior, rate limits, authentication needs, error handling, or whether it's a read-only operation. For a search tool with zero annotation coverage, this leaves significant gaps.

  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 two concise sentences with zero waste, front-loading the core purpose. Every word earns its place, though it could be slightly more informative without losing efficiency. It's appropriately sized for a search tool.

  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?

  Given no annotations, no output schema, and three parameters, the description is incomplete. It covers the basic purpose and return fields but misses behavioral traits (e.g., safety, limits), usage context versus siblings, and deeper parameter insights. For a tool with this complexity, it should provide more guidance to the agent.

  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 three parameters thoroughly. The description adds no parameter-specific information beyond what's in the schema. Baseline 3 is appropriate when the schema does the heavy lifting, but the description doesn't compensate with additional context like example queries or platform nuances.

  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 the action ('Search for AI agent skills') and resource ('on agentskill.sh'), with specific verb+resource pairing. It distinguishes from sibling 'get_skill' (which likely retrieves a specific skill) and 'get_trending' (which likely shows popular skills), but doesn't explicitly contrast with 'install_skill' beyond the different action. The purpose is specific but could be more differentiated.

  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 like 'get_skill' or 'get_trending'. It doesn't mention prerequisites, use cases, or exclusions. The agent must infer usage from tool names alone, which is insufficient for optimal selection.

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

• get_skillB
  3.2/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 mentions retrieving 'full details' including specific components, but doesn't disclose behavioral traits such as error handling (e.g., what happens if the slug doesn't exist), authentication needs, rate limits, or response format. This leaves gaps for an agent to understand operational nuances.

  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, efficient sentence that front-loads the purpose and lists key details retrieved. It avoids redundancy and wastes no words, though it could be slightly more structured by separating usage context.

  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 moderate complexity (retrieving detailed skill info), no annotations, and no output schema, the description is minimally adequate. It specifies what details are included, but lacks information on return values, error cases, or behavioral constraints, leaving the agent with incomplete context for reliable 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 input schema has 100% description coverage, with the 'slug' parameter well-documented in the schema. The description adds no additional parameter semantics beyond implying the slug identifies a 'specific skill', which is already clear from the schema. Baseline 3 is appropriate as the schema does the heavy lifting.

  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 the verb 'Get' and resource 'full details for a specific skill', specifying what information is retrieved (SKILL.md content, security info, metadata). It distinguishes from siblings like 'search_skills' (searching multiple) and 'install_skill' (installing), though not explicitly. However, it doesn't fully differentiate from 'get_trending' which might also retrieve skill details, keeping it at 4.

  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 detailed information for a specific skill, but provides no explicit guidance on when to use this tool versus alternatives like 'search_skills' for broader queries or 'get_trending' for trending skills. It lacks exclusions or prerequisites, relying on context from the tool name and parameters.

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