Server Quality Checklist

Tool Scores

• wpcliD
  1.9/5.0
  Behavior1/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 explaining behavior. It does not disclose that arbitrary WP-CLI commands may be executed, nor any security, destructive, permission, output, or error implications. For a command-passthrough tool this is a serious omission.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness2/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is short, but under-specification is not conciseness. The phrase 'WordPress CLI tool' is largely redundant with the tool name, and the sentence does not carry enough operational information to justify its brevity.

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

  Completeness1/5

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

  For a generic WP-CLI execution tool with no annotations, no output schema, and no behavioral notes, the description must explain usage, side effects, and expected results. It provides almost none of this, leaving the agent unable to predict consequences or outcomes.

  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%, and the schema already describes command as 'WP-CLI command to execute'. The description adds only the CreatorLMS scope and no additional syntax, examples, or constraints, so it does not go beyond the baseline.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose2/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description lacks a verb and mainly restates the tool name: 'WordPress CLI tool' adds no action such as execute, run, or manage. Scoping it to CreatorLMS adds context but does not say what the tool actually does.

  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 usage guidance is provided. The description never states when to use this tool instead of the sibling tools github or docs, despite those being plausible alternatives for different kinds of tasks.

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

• docsC
  2.6/5.0
  Behavior2/5

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

  With no annotations, the description carries the behavioral burden, but it says nothing concrete about return behavior, side effects, or access needs. The claim that it 'enforces rules' is not backed by the actual list/get/search actions and could mislead an agent into expecting enforcement rather than documentation retrieval.

  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 one short sentence with no filler and puts the core noun phrase first. However, the 'enforces rules' fragment is vague and does not fully earn its place as written.

  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 tool with no annotations and no output schema, the description is too thin: it does not explain what happens when each action is invoked, what kind of content is returned, or when the agent should consult it. The schema provides the action vocabulary, but the description leaves too much behavioral context to inference.

  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%, and each parameter already has a clear description and action is constrained to an enum. The description adds no parameter semantics, so the baseline 3 applies.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose3/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description identifies the resource (company documentation and best practices) and signals a normative purpose, but it lacks a specific operation verb like retrieve or read. It also says the tool 'enforces rules,' which is more suggestive than a clear definition of what calling the tool does.

  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 guidance on when to use this tool versus alternatives such as github or wpcli is provided. The phrase 'enforces rules for development' implies you should consult it for compliance, but the intended selection criteria are left implicit.

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

• githubC
  2.6/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 behavioral burden. It offers only 'pure remote operations', which hints that actions occur remotely, but does not disclose that actions like create_branch, create_pr, and update_file are mutating operations, nor any authentication, rate-limit, or side-effect information. The repository scope constraint (example-repo) is stated, but broader behavioral traits are absent.

  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 concise sentence with no wasted words, and the core scope (GitHub, remote operations, example-repo) is front-loaded. While terse, it is not padded or redundant, which fits the conciseness criterion. It loses a point because it is so brief that it omits essential detail, but it is still appropriately compact.

  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 tool's complexity—four parameters, seven actions, no output schema, and no annotations—the description is severely incomplete. It does not explain what any of the actions do, when to use them, what inputs they require, or what the results look like. The schema covers parameter names but not action semantics. An agent could not correctly plan a call without substantial unstated knowledge.

  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 each parameter has a description. The tool description, however, adds no value beyond the schema—it does not clarify how taskBranch relates to actions, what taskDescription means for file operations, or how the action enum values differ. Baseline 3 is appropriate because the schema already documents parameters, but the description does not enrich them.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose3/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description identifies the tool as a GitHub API integration for remote repository operations, and the repo scope example-repo, which gives a general sense of purpose. However, it relies on a noun phrase rather than a specific verb+resource, and the seven distinct operations are only discoverable by opening the schema. It is distinguishable from siblings (wpcli, docs) but does not state the actual capabilities.

  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?

  There is no explicit guidance on when to use this tool versus alternatives. The phrase 'GitHub API integration' weakly implies it is for GitHub-related tasks, but no when-to-use, when-not-to-use, or alternative conditions are provided. With siblings like wpcli and docs, an agent must infer selection purely from the tool name and description's mention of GitHub.

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