Server Quality Checklist

Tool Scores

• skillsmp_searchA
  3.6/5.0
  Behavior4/5

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

  Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds that results include name, description, author, stars, and GitHub URL, and explains pagination defaults and sorting. This extends transparency without contradiction.

  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 concise, starting with the purpose then listing parameters in a structured bullet-like format. It uses clear labels and examples without extraneous text. Could slightly benefit from better paragraph flow.

  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 5 parameters and no output schema, the description covers basic functionality (return fields, pagination, sorting) but lacks details on error handling, empty results, or rate limits. It is adequate for a simple search tool but not fully comprehensive.

  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. The description repeats schema descriptions for query, page, limit, sort_by and adds examples (e.g., 'fastapi', 'react testing') and clarifies defaults. However, no new semantic meaning beyond schema is provided.

  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 explicitly states the tool searches 'SkillsMP marketplace for AI coding skills by keywords', providing a specific verb (search) and resource (marketplace for coding skills). It clearly distinguishes from siblings like skillsmp_install_skill or skillsmp_list_repo_skills by focusing on search.

  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 sibling tools like skillsmp_ai_search or skillsmp_list_repo_skills. It lacks explicit advice on contexts or alternatives, leaving selection to the agent without criteria.

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

• skillsmp_install_skillA
  3.8/5.0
  Behavior3/5

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

  Annotations already indicate readOnlyHint=false, so the description correctly implies a write operation. It adds details about installation scope (project vs global) but does not mention side effects like overwriting existing skills or required 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?

  The description is concise with a front-loaded purpose, followed by parameter details and an example. Every sentence adds value without 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 tool with 4 parameters and no output schema, the description provides adequate purpose, parameter details, and an example. It lacks information on return values or error handling, but is otherwise complete.

  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. The description rephrases parameters and adds an example but does not significantly extend meaning beyond the schema descriptions (e.g., valid agents are listed in schema too).

  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 'Install skills from GitHub to AI coding agents,' which is a specific verb-resource pair. It distinguishes from sibling tools like skillsmp_ai_search or skillsmp_get_skill_content by focusing on installation.

  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 explains parameters and provides an example but does not explicitly state when to use this tool versus alternatives or when not to use it. Usage is implied but not formally guided.

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

• skillsmp_ai_searchA
  4/5.0
  Behavior3/5

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

  Annotations already declare readOnlyHint, idempotentHint, etc. Description adds the semantic search aspect but no additional behavioral details like pagination or result format. Adequate but not enhanced.

  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?

  Very concise: short paragraph, parameter list, and examples. No wasted words, well-organized for easy scanning.

  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 search tool without output schema, description provides input guidelines, examples, and response_format parameter hint. Could mention return type (list of skills) but overall 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 descriptions already cover both parameters (100% coverage). Description adds example queries which provide context but does not add significant new semantics 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?

  The description clearly states the tool performs semantic search for skills using natural language queries. It distinguishes from sibling tools like skillsmp_search by emphasizing intent understanding and contrast with keyword search.

  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 says 'Use this when keywords aren't enough' providing clear when-to-use guidance. Includes examples but does not explicitly name alternative tools.

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

• skillsmp_list_repo_skillsA
  4/5.0
  Behavior4/5

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

  Annotations already declare read-only, non-destructive, idempotent, and open-world. Description adds that it returns skill names and descriptions, providing useful behavioral detail beyond annotations.

  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?

  Short and to the point, but the parameter list duplicates schema info, slightly reducing conciseness.

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

  Completeness5/5

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

  For a simple list tool with comprehensive annotations, the description fully covers purpose, parameter, and return content. No gaps identified.

  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 a clear description for the source parameter. The description provides an example (anthropics/claude-code) but doesn't add significant new meaning.

  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?

  Clearly states the action (list), resource (skills in a repository), and a key distinction (without installing). Differentiates from sibling install_skill.

  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?

  Implicitly suggests use when exploring repository skills before installation, but lacks explicit when-to-use versus alternatives like search.

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

• skillsmp_get_skill_contentA
  4.4/5.0
  Behavior4/5

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

  Annotations already provide readOnlyHint=true and idempotentHint=true, indicating safe reads. The description adds valuable behavioral details beyond annotations, such as 'If path has no skill.md, returns directory listing,' which helps the agent understand fallback behavior.

  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 concise at 6 sentences, front-loaded with the main purpose, then a parameter list with examples, and finally an edge-case behavior. Every sentence adds value without 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 read-only preview tool with 4 parameters and no output schema, the description covers parameters, fallback behavior, and usage context. It could mention that the content is raw markdown, but that is implied by 'reads skill file content.' Overall, it is sufficiently complete.

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

  Parameters4/5

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

  Schema description coverage is 100%, so baseline is 3. The description adds concrete examples for each parameter (e.g., 'owner: GitHub username/org (e.g., "anthropics")' and path examples), which adds meaning beyond the schema's basic descriptions.

  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 it reads skill file content (SKILL.md) from a GitHub repository for previewing before installation. The verb 'read' and resource 'skill file content' are specific, and the context 'from a GitHub repository' is unambiguous. It distinguishes from sibling tools like install and list.

  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 states 'Use to preview a skill before installing,' which provides clear when-to-use guidance. Sibling tools like install and list are implied alternatives, but no explicit when-not-to-use or exclusions are given.

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