Server Quality Checklist

Tool Scores

• get_github_activityA
  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 discloses that the call is live, external, and returns public repositories, and that it defaults to Daksh's username. However, it does not mention rate limits, failure behavior, or the shape of the returned repository list.

  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 sentences, with the core purpose front-loaded. The parenthetical about being a 'bonus tool' is somewhat meta and not essential for invocation, but it does help explain why this tool exists alongside static profile tools.

  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 read-only external API fetch with 0 required parameters and full schema coverage, the description covers purpose, source, liveness, and default behavior. With no output schema or annotations, a bit more detail about the returned repository fields would strengthen it, but it is largely sufficient for an agent to invoke the tool correctly.

  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%: both 'limit' and 'username' are documented in the schema, including defaults. The description adds only the contextual detail that the username defaults to Daksh's, which is already in the schema, so no significant value is added beyond the structured input.

  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?

  States a specific verb and resource: 'Fetches a live list of recently updated public repositories for a GitHub user'. It clearly distinguishes itself from the sibling profile/experience/static-data tools by emphasizing 'live' and 'not static profile data'.

  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?

  Provides clear context that this is for live external GitHub API data rather than static profile data, which implies when to use it over siblings. It does not explicitly name alternative tools or formalize exclusions, but the 'not static profile data' phrasing gives practical routing guidance.

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

• get_skillsA
  4/5.0
  Behavior3/5

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

  With no annotations, the description carries the behavioral burden. It discloses that results are grouped by category and that filtering is optional, which is useful. However, it does not describe response format, error behavior, or whether the category list is exhaustive, leaving some behavioral detail to inference for a simple read operation.

  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, efficient sentence that front-loads the core purpose and immediately follows with the filtering option. No redundant wording or filler. The 'etc.' is slightly vague but acceptable in context.

  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 one optional parameter and no annotations or output schema, the description sufficiently explains what the tool returns and how to invoke it. It could briefly mention that the output is a grouped structure, but 'grouped by category' already conveys that. Overall, an agent has enough to call it correctly.

  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 fully documents the category parameter. The description adds no new meaning beyond restating the optional filter, which is the baseline expected when the schema carries full parameter detail.

  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 states a specific verb ('Returns') and resource ('Daksh's skills') with a clear grouping behavior. It distinguishes itself from sibling tools like get_profile and list_projects by focusing on skills, making the tool's purpose 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 when to use this tool: whenever an agent needs Daksh's skills. It provides no exclusion or alternative because none of the sibling tools cover skills. The optional filter guidance adds context for narrowing the call, though it does not explicitly compare against alternatives.

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

• list_projectsA
  4/5.0
  Behavior3/5

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

  With no annotations available, the description carries the burden of behavioral disclosure. It does disclose the output shape ('Each project includes description, role, tech stack, highlights, and links') and the optional filters. However, it does not mention ordering, behavior when no projects match, or whether the list follows any deterministic order, leaving some traits to inference.

  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 two sentences with no filler. The main action 'Lists Daksh's projects' is front-loaded, and each sentence adds a distinct piece of information: optional filters and the returned fields.

  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 read-only listing tool with two optional parameters and no output schema, the description is nearly complete. It enumerates the fields returned in each project and mentions both optional filters. Minor gaps like explicit ordering or empty-result behavior keep it from a perfect score.

  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%; both 'tag' and 'limit' already have descriptive text in the schema. The tool description only adds a marginal example tag value ('fintech') and refers to limit as a cap, which does not substantially exceed the schema baseline.

  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 'Lists' with a clear resource 'Daksh's projects', and immediately specifies optional filtering by tag and capping by limit. This clearly distinguishes it from sibling tools like get_profile, get_experience, get_skills, and get_github_activity, which cover different domains.

  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: this is the tool for retrieving Daksh's projects, optionally narrowed by tag and limit. It does not explicitly name alternatives or exclusion conditions, but the domain difference from the listed siblings makes selection unambiguous.

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

• get_experienceA
  4.2/5.0
  Behavior4/5

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

  With no annotations provided, the description carries the full behavioral disclosure burden. It communicates that the operation is a read-only retrieval, lists output content, and notes the optional filtering behavior. It doesn't mention edge cases like missing experience or unknown company names, but this is adequate for a simple getter.

  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 concise, well-structured sentences with no filler. The key action and return fields are front-loaded, and the optional filter is stated efficiently.

  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 single-optional-parameter read-only tool with no output schema and no annotations, the description covers the essential invocation context: what is returned, from whom, and how filtering works. It could go slightly further by describing the response shape or ordering, but nothing critical is missing.

  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 the 'company' parameter thoroughly, including case-insensitive partial match behavior. The description only restates the optional filtering concept without adding 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?

  The description uses a specific verb 'Returns' with a clear resource ('Daksh's work history') and enumerates the exact fields included: company, title, dates, summary, and achievements. This clearly distinguishes it from siblings like get_profile and list_projects.

  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 states that the tool returns work history and optionally filters to a single company, giving the agent a solid sense of when to use it. It doesn't explicitly name sibling tools or mention when not to use it, but the domain is obvious enough.

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

• get_profileA
  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 the behavioral transparency burden. It clearly states that the tool returns identity information, implying a read-only operation, but it does not explicitly mention response format, error behavior, or side-effect absence. The risk is low for a simple profile getter, and the return content is specified.

  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 two sentences with no filler. The core action and content are front-loaded, and the usage note is directly actionable.

  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?

  Because there is no output schema, the description carries the responsibility of indicating what the tool returns. It lists the main identity fields and provides usage guidance, which is sufficient for this simple tool. Some minor specifics like exact link names or formatting are omitted but not critical.

  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?

  The tool has zero parameters, so the description does not need to explain parameter meaning. The baseline of 4 applies because there is no input complexity for the agent to navigate.

  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 ('Returns'), names the exact resource ('Daksh's professional identity'), and enumerates the content: name, title, summary, location, and contact/social links. This clearly differentiates it from sibling tools like list_projects, get_experience, get_skills, and get_github_activity.

  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 instructs to use this tool first for any 'who is this person' question, providing a clear usage context. It does not explicitly state when not to use it or name alternative tools, but the sibling set makes the boundary obvious.

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