Server Quality Checklist

Tool Scores

• pcloud_create_public_linkC
  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 the full burden of behavioral disclosure. It mentions the tool 'creates' a 'public' link, implying a mutation that exposes content publicly, but it does not explain consequences, permissions required, link persistence, or reversibility. This is a significant gap 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?

  The description is a single, concise sentence with no redundant words. It is front-loaded with the main action and object. While it is underspecified, the structure itself is efficient and appropriate for the minimal content provided.

  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?

  This is a mutation tool with no output schema and no annotations. The description does not explain what the tool returns, how the link behaves, whether it is permanent, or any side effects. Given the simple schema, the description is insufficient for an agent to fully understand the tool's impact and expected output.

  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 both parameters with descriptions (100% coverage), including the 'type' enum and default. The description's mention of 'file or folder' merely mirrors the 'type' parameter and adds no additional meaning beyond what the schema already provides, so it stays at the baseline.

  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 (create) and resource (public sharing link for a file or folder). It is specific enough to understand the tool's purpose, but it does not distinguish this from the sibling tool 'pcloud_get_file_link', which also deals with links. Thus it is clear but lacks sibling differentiation.

  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 pcloud_get_file_link, nor does it mention any prerequisites or exclusions. There is no implied usage context beyond the basic action, so it offers minimal decision support.

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

• pcloud_get_file_infoC
  2.9/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 for behavioral disclosure. It states 'Get' which implies a read operation, but does not disclose whether authentication is required, what specific metadata fields are returned, or any limitations. The description is too sparse to provide meaningful transparency.

  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 sentence with no redundant words. It is front-loaded and appropriately sized for a simple tool, though it sacrifices useful detail for brevity. Every word earns its place, but the overall structure is minimal.

  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?

  There is no output schema, so the description should explain what information the agent will receive. It does not state the return format, the fields included in the metadata, or any error conditions. Given the tool's simplicity, this is a notable gap that leaves the agent uncertain about the tool's output.

  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% coverage with a single required parameter 'path' described as 'Path of the file'. The description adds no extra meaning beyond this. Since schema coverage is high, the baseline of 3 applies, but the description fails to enrich the parameter semantics further.

  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 the resource 'metadata/information about a file in pCloud'. It distinguishes from siblings that perform actions (delete, rename, copy, create links) but is somewhat vague about what 'metadata' entails, making it less differentiated from tools like get_file_link or get_checksum.

  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 guidance on when to use this tool versus alternatives. The description is declarative only and does not mention use cases, prerequisites, or exclusions. Since no information is provided, the agent must guess based on the tool name alone.

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

• pcloud_copy_folderB
  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 of behavioral disclosure. It only states the basic action without explaining recursion, overwrite behavior, or what happens when the destination exists, which are important for a copy 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?

  The description is a single, direct sentence with no redundant words. It is front-loaded with the verb and resource, making it easy to parse quickly.

  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 copy operation with no annotations or output schema, the description lacks crucial behavioral details such as whether the folder contents are copied, handling of existing destinations, and return value. The schema covers parameters but not behavior, leaving the description incomplete for a mutation tool.

  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 both parameters at 100%, so the baseline is 3. The description adds no additional semantics beyond the schema's 'path' and 'toPath' descriptions, but it does not need to compensate.

  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 action (copy) and resource (folder) with a destination, distinguishing it from sibling tools like pcloud_copy_file and pcloud_rename_folder. It is specific and unambiguous.

  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 gives no guidance on when to use this tool versus alternatives such as pcloud_copy_file or pcloud_move_folder. It does not mention conditions, prerequisites, or exclusions, leaving the choice entirely to the agent's inference.

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

• pcloud_create_folderB
  3.2/5.0
  Behavior2/5

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

  With no annotations provided, the description carries the full burden of behavioral disclosure, but it only states 'Create a new folder' and does not mention what happens on conflicts, whether parents are created automatically, or what the tool returns. This is a significant gap for a mutating 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?

  The description is a single, direct sentence with no unnecessary words. It is front-loaded and easily parsed.

  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 minimal. It fails to explain return values, error conditions, or any behavioral side effects, making it inadequate for an agent to anticipate the tool's full behavior.

  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% coverage, documenting the 'path' parameter with a clear example. The description adds no additional parameter semantics, so the baseline score 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 operation: 'Create a new folder in pCloud.' It uses a specific verb (create), a specific resource (folder), and a location (pCloud), distinguishing it from siblings like pcloud_delete_folder or pcloud_list_folder.

  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, prerequisites (e.g., whether parent directories must exist), or any exclusions. It merely restates the operation without contextual advice.

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

• pcloud_delete_fileB
  3.2/5.0
  Behavior2/5

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

  No annotations are present, so the description carries full responsibility. It discloses that the tool deletes a file but does not mention whether deletion is permanent, if special permissions are required, or what happens to related metadata.

  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 focused sentence that directly states the tool's purpose without extraneous wording.

  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 low complexity of the tool and the presence of a schema, the description is minimally acceptable but lacks critical details for a destructive operation, such as irreversibility and error conditions.

  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 schema fully describes the single parameter (`path` with description 'Path of the file to delete'). The tool description adds no additional semantic detail about the parameter, so the 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 with a specific verb ('Delete') and object ('file'), distinguishing it from sibling tools like pcloud_delete_folder and pcloud_rename_file.

  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 context is provided. The description does not indicate when to prefer this tool over siblings, nor does it mention any prerequisites or alternatives.

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

• pcloud_copy_fileB
  3.3/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 only says 'copy', which implies a new file creation, but does not disclose overwrite behavior, required directory existence, access permissions, or return value. This is minimal intent without operational detail.

  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 states the operation without unnecessary words. It is appropriately concise for the simplicity of the tool.

  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 low complexity (two required parameters, no output schema, no annotations), the description is minimally adequate but lacks behavioral details such as what happens if the destination exists or what is returned. These gaps prevent a higher score, though the schema covers parameter semantics.

  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 provides complete descriptions for both parameters (path and toPath, 100% coverage). The description adds no additional parameter semantics, but the schema is sufficient, so a baseline score of 3 is appropriate.

  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 the verb 'Copy' with the resource 'a file' and specifies 'to another location in pCloud', clearly conveying the operation and distinguishing it from sibling tools like pcloud_copy_folder. It goes beyond the tool name by adding the destination detail.

  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 pcloud_rename_file or pcloud_copy_folder. There is no mention of prerequisites, conflict behavior, or exclusions, leaving the agent to infer usage solely from the tool name.

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

• pcloud_read_text_fileB
  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 of behavioral disclosure, but it only says 'read contents' without detailing error handling, return format, permissions, or file type support. This lack of context could lead to incorrect assumptions about edge cases.

  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 redundancy. Every word earns its place.

  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 one-parameter read operation, the description and schema convey the essential purpose. However, given the absence of an output schema and annotations, a brief note on return format or error behavior would improve completeness, but the current level is nearly 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?

  The schema fully covers the single path parameter with a clear description ('Path of the text file to read'), achieving 100% coverage. The description adds no additional parameter information, so the baseline score of 3 is appropriate.

  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 a specific action (read) and resource (text file from pCloud), distinguishing it from sibling tools that handle metadata, deletion, renaming, or linking. It is unambiguous and directly reflects the tool's function.

  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 is provided on when to use this tool versus alternatives like pcloud_get_file_info or pcloud_get_file_link. The description does not mention prerequisites, exclusions, or typical usage scenarios, leaving the agent to infer context from the name alone.

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

• pcloud_get_file_linkA
  3.5/5.0
  Behavior3/5

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

  No annotations are present, so the description carries the full burden. It adds the key behavior that the link is temporary, which is useful. However, it does not disclose details such as link expiration period, authentication requirements, or error behavior. This is a minimal but non-empty 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 a single sentence that is front-loaded with the verb 'Get' and directly describes the resource. No wasted words or redundancy.

  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 simple tool with one parameter and no output schema, the description covers the basic purpose but lacks guidance on when to use it over create_public_link and does not describe the return value format or link characteristics. It is minimally complete but leaves ambiguities.

  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% for the single parameter, with the property description clearly defining 'path'. The tool description adds no additional meaning beyond the schema, so a baseline score of 3 is appropriate.

  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: obtaining a temporary download link for a file in pCloud. It distinguishes this from sibling tools like pcloud_create_public_link (which creates a public link) and pcloud_get_file_info (which retrieves metadata).

  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 is provided on when to use this tool versus alternatives. There is no mention of when not to use it or how it differs from creating a permanent public link, leaving the agent without explicit selection criteria.

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

• pcloud_rename_fileA
  3.5/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 only states that the tool renames or moves a file, without mentioning potential side effects, permission requirements, overwrite behavior, return values, or error conditions. This lack of context for a mutating operation is a significant gap.

  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 entire description is one short, direct sentence with no superfluous words or repetition. It is appropriately sized for a straightforward file operation, maximizing readability and agent comprehension.

  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 simplicity of the operation, the description covers the primary action and parameter intent sufficiently. However, it omits information about return values, success/failure indicators, and potential edge cases (e.g., moving to an existing path), which could matter for an agent deciding whether additional verification is needed. The absence of an output schema increases this burden.

  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 for parameters is 100%, and both 'path' and 'newPath' already have concise descriptions explaining their roles. The tool description adds no extra semantic meaning beyond what the schema provides, matching the baseline for well-documented 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 clearly states the verb ('Rename or move') and the resource ('a file in pCloud'), making the tool's purpose immediately evident. It also distinguishes itself from sibling folder-level tools like pcloud_rename_folder by explicitly limiting scope to files.

  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 renaming or moving a file, which is clear enough for basic selection. However, it does not explicitly mention alternatives (e.g., pcloud_copy_file for copying, pcloud_delete_file for removal) or provide when-not-to-use scenarios, relying on the agent to infer context.

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

• pcloud_rename_folderA
  3.5/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 of behavioral disclosure. It merely says 'rename or move' without detailing side effects, safety profile, or potential errors (e.g., whether the operation can overwrite existing folders or requires authentication). This is insufficient 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.

  Conciseness5/5

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

  The description is a single concise sentence that is front-loaded and contains no redundant information. It efficiently conveys the core purpose.

  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?

  The tool is simple with two well-documented parameters and no output schema. However, the description lacks usage guidance and behavioral details that could help an agent invoke it safely. It is minimally sufficient but not 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?

  The schema already provides complete descriptions for both parameters (path: 'Current path of the folder'; newPath: 'New path/name for the folder'), and the tool description adds no extra meaning. With 100% schema coverage, the baseline of 3 is appropriate.

  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 action (rename or move) and the resource (a folder in pCloud). It distinguishes from sibling tools by explicitly targeting folders, unlike pcloud_rename_file which is for files.

  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 renaming or moving folders but does not explicitly mention when to use it over alternatives like pcloud_rename_file or pcloud_copy_folder. The context from sibling names suggests the use case, but no explicit guidance is provided.

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

• pcloud_searchA
  3.5/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 full responsibility for behavioral disclosure. It only mentions searching by name, omitting important details like recursive search, case sensitivity, or whether it searches within the specified path. This is insufficient for an agent to predict behavior beyond the basic 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?

  The description is a single, clear sentence with no redundant words or repetition. It is appropriately front-loaded and concise, earning a top score.

  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 simple search tool with 2 params and no output schema, the description provides the core purpose but lacks context on search behavior (e.g., recursion, path scope). While the schema covers parameter details, the overall description is adequate but not complete enough to fully anticipate the tool's behavior.

  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 already provides complete descriptions for both parameters (query and path) with 100% coverage. The description adds no extra meaning beyond what the schema states, so it meets the baseline but does not enhance parameter understanding.

  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 specific function: searching for files and folders by name. This distinguishes it from siblings like list_folder or file lookup tools, making its 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 Guidelines3/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description implies usage for name-based search, but it does not explicitly state when to choose this over alternatives like list_folder, nor does it mention exclusions or prerequisites. The usage guidance is minimal and inferred rather than explicit.

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

• pcloud_delete_folderA
  3.7/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 responsibility for behavioral disclosure. It states the action and the recursive flag, but fails to mention critical aspects such as whether deletion is permanent or reversible, error behavior for non-existent paths, or what happens if recursive=false on a non-empty folder. This is a significant gap for a destructive 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?

  The description is extremely concise—two sentences, front-loaded with the action and a focused note on the recursive parameter. Every word earns its place, with no unnecessary detail or repetition.

  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 simple two-parameter tool, the description is adequate but not complete. It clearly covers purpose and the recursive flag, but lacks behavioral details like permanence, error handling, and exact behavior for non-empty folders without recursive. Given the absence of annotations and output schema, these gaps make it a minimum viable description rather than a fully comprehensive one.

  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 fully documents both parameters. The description adds a slight semantic clarification about recursive behavior, but this largely restates the schema's description. Baseline of 3 is appropriate as the description provides minimal added value beyond the structured 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's action ('Delete a folder from pCloud') and resource, distinguishing it from sibling tools like pcloud_delete_file. The verb is specific and the intent is 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 provides a clear usage note for the recursive parameter ('Use recursive=true to delete non-empty folders'), offering context on when to set it. However, it does not explicitly mention alternative tools (e.g., pcloud_delete_file) or when to choose this over others, so it lacks explicit exclusions.

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

• pcloud_list_folderA
  3.8/5.0
  Behavior3/5

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

  With no annotations provided, the description must carry the burden of behavioral disclosure. It correctly implies a read-only operation by saying 'List contents,' but it does not disclose potential side effects (e.g., API rate limits), error behavior on invalid paths, or the impact of the 'recursive' flag. The description adds some context (returns metadata) but lacks deeper behavioral detail.

  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 long, front-loaded with the primary action ('List contents of a folder in pCloud'), and contains no fluff or repetition. Every word adds value.

  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?

  This is a simple 2-parameter tool with no output schema. The description covers the main purpose and return value at a high level ('files and subfolders with their metadata'), but it does not explain recursive behavior, error handling, or the exact metadata structure. Given the tool's simplicity and schema completeness, this is nearly complete but could be slightly more explicit.

  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 provides 100% coverage for both parameters ('path' and 'recursive'), each with clear descriptions. The tool description itself does not add meaningful parameter-level information beyond what the schema already contains, so the baseline score of 3 is appropriate.

  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 ('List') and resource ('contents of a folder in pCloud'), clearly distinguishing it from sibling tools like pcloud_get_file_info (single file) and pcloud_search. It also mentions the return type (files and subfolders with metadata), making the purpose unmistakable.

  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 (listing a folder's contents) but does not explicitly state when to choose this over alternatives, nor does it mention exclusions or limitations. For example, it doesn't say 'use pcloud_search for cross-folder queries' or 'not for retrieving a single file's info'.

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

• pcloud_get_checksumA
  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 full burden. It clearly states the action (get checksums) but does not disclose any additional behavioral traits such as read-only nature, potential file size limits, or authentication requirements. For a simple read operation this is acceptable but not particularly informative.

  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, concise sentence that fully communicates the tool's purpose with no wasted words. It is front-loaded with the action and resource.

  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 the tool's simplicity (one parameter, no output schema, no nested objects), the description sufficiently explains what the tool does and what it returns (checksums). It does not detail return formatting, but for a basic getter this is adequate.

  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 parameter 'path' is described in the schema as 'Path of the file to get checksum for'. The tool description adds no additional meaning beyond what the schema already provides, so the baseline score of 3 is appropriate.

  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 'Get' and a specific resource 'checksums for a file', clearly distinguishing it from sibling tools that retrieve file info, user info, or perform file operations. It explicitly names the three checksum types (SHA256, SHA1, MD5), leaving no ambiguity.

  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 implies the tool should be used when a file's checksums are needed, which is a clear context. However, it does not explicitly state when not to use it or mention alternatives among the sibling tools, though the uniqueness of checksum retrieval makes the usage context fairly obvious.

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

• pcloud_get_user_infoA
  4.2/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 behavioral disclosure. The verb 'Get' implies a read-only operation, and the mention of 'authenticated user' indicates authentication is involved. However, it doesn't explicitly state that no changes are made or describe any potential side effects, leaving some ambiguity.

  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, direct sentence that immediately conveys the core purpose. It is concise and front-loaded, with no unnecessary words.

  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 tool with no parameters, no annotations, and no output schema, the description is sufficient in scope. It names the resource (user info) and a key detail (quota usage), which covers the essential use case. However, it could be more complete by listing other possible returned fields, but this is not critical given the tool's simplicity.

  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 need not explain parameter usage. The baseline for 0 params is 4, and the description appropriately makes no redundant parameter references.

  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: to get information about the authenticated pCloud user, specifically mentioning quota usage. This distinguishes it from sibling tools that focus on files and folders.

  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: it is used to retrieve user account information. While it doesn't explicitly mention alternatives, the sibling tools are all file/folder operations, so the usage is unambiguous. No exclusion criteria are needed.

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