Server Quality Checklist

Tool Scores

• watchB
  3.4/5.0
  Behavior2/5

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

  With no annotations, the description carries the full burden. It discloses that the tool 'watch[es]' and 'auto-process[es]', but does not clarify key behavioral traits such as whether it runs indefinitely, how it handles errors, whether existing files are processed, or what the return/exit behavior is. The description is too brief to give a complete behavioral picture.

  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, front-loaded sentence that efficiently states the tool's purpose without superfluous details. Every word contributes to understanding the tool's core function.

  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?

  Despite having a nested config object and no output schema, the description does not explain what happens when the watch runs (e.g., does it block, return a handle, list processed files?). It also doesn't clarify how config is used in practice, such as defaults or required subfields for each action. The tool is more complex than the description conveys, leaving gaps in context.

  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 baseline is 3. The description adds minimal value beyond the schema: it names the actions (rename, pdf-split) but the schema already enumerates them. The config object is not elaborated beyond the schema, so no additional semantic insight 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 clearly states the tool's function: 'Watch a directory for new files and auto-process them' with specific verbs and resources. It differentiates from sibling tools by mentioning 'rename or pdf-split', which are separate tools, indicating this is a higher-level watcher that dispatches to them.

  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 for monitoring a directory and automatically applying actions, but does not explicitly state when to use this instead of directly calling rename or pdf-split, nor does it mention exclusions or prerequisites. It provides context (new files) but lacks clear guidance on alternatives.

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

• pdf_splitA
  3.7/5.0
  Behavior3/5

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

  The description adds a key behavioral trait by disclosing that the PDF is sent to the renamed.to API for processing, which is useful context. However, with no annotations, it does not disclose whether the operation is read-only, modifies the original file, is asynchronous, or has any rate limits or side effects. The external API mention is a positive but insufficient disclosure.

  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, front-loaded with the core purpose and strategy options. The second sentence adds essential external API context. Every word earns its place; there is no redundancy or filler.

  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?

  For a tool that sends PDFs to an external API and has no output schema, the description is somewhat incomplete. It does not mention whether the operation returns anything, how to monitor progress (potentially via sibling 'status'), or whether the original file is modified. This would be clearer with a note on asynchronous behavior or output handling.

  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 all parameters have descriptions (e.g., strategy enum values). The description's mention of 'content or topic using AI, bookmarks, or page ranges' aligns with the enum values but does not add any new semantics beyond what the schema already provides. Baseline of 3 applies.

  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 function: 'Split PDFs by content or topic using AI, by bookmarks, or by page ranges.' It uses a specific verb (split), a specific resource (PDFs), and lists the main modes. This clearly distinguishes it from sibling tools like rename, watch, and status.

  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 by listing splitting strategies (content/topic, bookmarks, page ranges), but it does not explicitly state when to use this tool versus alternatives or provide any exclusions. It lacks context such as prerequisites, typical use cases, or when not to use it.

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

• renameA
  3.8/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 burden of behavioral disclosure. It usefully reveals that files are sent to an external API, which is a key behavioral trait. However, it does not mention dry-run behavior, handling of original files, or output directory semantics, leaving some gaps.

  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, front-loading the core purpose and adding the API detail. Every word contributes value, with no redundancy or filler.

  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 no annotations and no output schema, the description provides essential context by naming the external service and explaining the AI analysis. It covers the tool's unique behavior well, though it omits potential side effects like network requirements or preview modes, but these are not strictly necessary given the schema coverage.

  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 covers all parameters with descriptions (100% coverage), so the description adds little to parameter understanding. It merely reinforces the purpose without providing additional semantic detail beyond the schema's existing 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?

  The description clearly states the tool's function: renaming files via AI content analysis via the renamed.to API. The verb 'Rename' and the resource 'files' are specific, and the mention of AI analysis distinguishes it from sibling tools like pdf_split, watch, and status.

  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 by specifying 'using AI content analysis' but does not explicitly state when to use this tool versus alternatives or when not to use it. No exclusions or alternative tools are mentioned, leaving usage somewhat inferred.

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

• statusA
  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 burden of disclosing behavioral traits. It states what the tool checks (auth status and API connectivity), but does not describe side effects, return format, or whether it is read-only. This is adequate but lacks depth for a tool with no structured annotations.

  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, tightly worded sentence that gets straight to the point. Every word adds meaning, no fluff or redundancy, and it is front-loaded with the verb 'Check'.

  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 no parameters and no output schema, the description provides the essential purpose and services checked. It does not detail return values, but for such a simple diagnostic tool, the agent can invoke it without ambiguity. A minor gap is the lack of information about the response structure, but overall it is complete enough for selection and invocation.

  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, and schema coverage is trivially 100%. With no parameters to explain, the description does not need to add parameter-level semantics. The baseline of 4 applies, and the description correctly focuses on the tool's behavior rather than nonexistent parameters.

  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 ('Check') and clearly identifies the resource: authentication status and API connectivity for the renamed.to service. This unambiguously distinguishes it from sibling tools like pdf_split, rename, and watch, which are action-oriented.

  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 when to use the tool—when you need to verify service status or connectivity—but it does not explicitly state when to use it versus alternatives. There are no exclusions or alternative mentions, so usage guidance is only implied rather than explicit.

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