Server Quality Checklist

Tool Scores

• workspace_get_file_contextA
  4.3/5.0
  Behavior4/5

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

  Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds value by detailing the two signal types (fragility and co-change) and explaining that 'fragile:false with empty partners' is a valid, non-error response. No contradictions.

  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 well-structured with bullet points and clear sections. Every sentence serves a purpose, and the length is appropriate for the complexity.

  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?

  Despite no output schema, the description provides a detailed return JSON structure and explains edge cases (no history, file not indexed). It is complete for a read-only informational 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?

  Schema coverage is 100% and already describes the path parameter well. The description does not add additional semantics beyond restating the parameter. Baseline 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 returns 'behavioral intelligence' about a single file, combining fragility and co-change signals. It distinguishes itself from siblings like workspace_assess_change and workspace_list_fragile_files.

  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 says 'Call this before editing or creating a file' and provides guidance on interpreting results (minimal changes for fragile, treat co-change partners as candidates). It lacks explicit exclusion of when not to use, but the context is clear.

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

• workspace_assess_changeA
  4.6/5.0
  Behavior5/5

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

  Annotations (readOnlyHint=true, idempotentHint=true, destructiveHint=false) are fully consistent with the description, which adds valuable context: the tool never certifies a change as safe, and it clarifies that 'none' is not a safety approval. The decision semantics are detailed, disclosing the mechanical enforcement logic. No contradictions found.

  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 fairly long but well-structured using bullet points for decision semantics and a JSON block for the return value. The purpose is front-loaded in the first sentence. While each sentence adds value, some redundancy exists (e.g., the return JSON is described both in text and in a code block). Still, it remains readable and informative.

  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?

  Given the absence of an output schema, the description provides a detailed return JSON structure with field descriptions, ensuring the agent understands what to expect. The tool's single parameter is fully covered by schema and description additions. The decision semantics are thoroughly explained, leaving no ambiguity about the tool's behavior.

  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 input schema has 100% coverage, describing the paths parameter with type, items, minLength, and maxItems. The description adds context beyond the schema, specifying 'repo-relative or absolute paths' and 'in the proposed change (1-200)', which helps the agent understand acceptable input. However, it does not explain how paths are resolved or validated further.

  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 purpose: 'Evaluate a SET of file paths…against workspace.json fragility and co-change history, and return a mechanical enforcement decision.' It uses a specific verb ('evaluate') and resource ('changeset'), distinguishing it from sibling tools like workspace_get_file_context (single file context) and workspace_list_fragile_files (listing fragile files).

  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 explains decision semantics and when each applies (e.g., deny, warn, annotate, none). It implies usage for proposed changes but does not explicitly state when not to use or mention alternatives like the sibling tools. The context signals and sibling names provide implicit guidance, but the description could be more explicit about exclusions.

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

• workspace_list_fragile_filesA
  4.6/5.0
  Behavior5/5

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

  The description discloses sorting order (most fragile first), default limit, and response format. Annotations already declare readOnlyHint and destructiveHint, so no contradiction. The description adds valuable behavioral context 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?

  The description is reasonably concise and front-loaded with the main action. Including the full return JSON is helpful but adds length; still, every sentence serves a purpose.

  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?

  Despite lacking an output schema, the description provides the complete return format and key behavioral details. Given the simple parameters and clear annotations, the description is sufficiently complete for accurate invocation.

  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 'limit', with default and maximum defined. The description restates these but adds no new semantic meaning beyond what the schema provides.

  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 lists fragile files from workspace.json sorted by score. It distinguishes from sibling tools like workspace_assess_change, workspace_get_cochange_partners, and workspace_get_file_context by focusing on a specific subset of files.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines5/5

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

  Explicit usage guidance is provided: 'Use for orientation at the start of a task: it tells you which parts of the codebase carry the most historical risk.' This tells when it should be used and its purpose.

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