Server Quality Checklist

Tool Scores

• get_projectC
  2.9/5.0
  Behavior2/5

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

  With no annotations, the description must carry the full behavioral burden. 'Get complete project details' implies a read operation, but it does not disclose side-effect-freeness, authorization requirements, potential errors, or what 'complete' entails. This is thin for a tool with no annotation safety signals.

  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 filler, and the core action and resource are front-loaded. It is appropriately concise for the tool's simplicity, though 'complete' is slightly vague and could be more specific.

  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 one-parameter retrieval tool, the description is minimally adequate. However, without annotations or an output schema, it lacks explicit behavioral and usage context, such as how projectId is used, what 'complete details' includes, and how it differs from list_all_projects.

  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%; the projectId parameter is documented in the schema. The description adds no additional parameter meaning, but since the schema already covers the single parameter, the baseline of 3 is appropriate.

  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 uses a specific verb ('Get') and a clear resource ('project'), and the word 'complete' signals it returns full details for a single project. It is reasonably distinguishable from siblings like list_all_projects, though it does not state the unique retrieval-by-ID behavior explicitly.

  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 given about when to use this tool versus alternatives. It does not mention that list_all_projects is for enumerating projects, nor does it explain that this tool is for fetching one project's details. The agent must infer usage from the tool name and sibling names.

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

• update_outlineB
  3.4/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 'update' and 'existing', without explaining whether the entire outline is replaced, whether partial updates are supported, what happens if the project does not exist, or what the response looks like. For a mutation tool, this 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 description is one clean sentence with no filler, and the action and target are front-loaded. 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.

  Completeness2/5

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

  Even with full schema coverage, this is a mutation tool with no annotations and no output schema. An agent would not know whether the outline is overwritten wholesale, whether the operation is reversible, or what a successful update returns. Additional behavioral context 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 projectId and outline. The description adds no further parameter semantics, such as the required structure of outline pages or whether the update is a full replacement.

  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 action ('Update') on a specific resource ('an existing project outline'), and 'existing' clearly distinguishes it from generate_outline, which creates a new outline. It also differentiates it from the get/list and image-generation siblings.

  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 this tool should be used when an outline already exists and needs modification, but it does not explicitly say when to use it versus generate_outline, nor does it mention alternatives or exclusions. Usage guidance is left mostly to inference.

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

• list_all_projectsA
  3.5/5.0
  Behavior2/5

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

  There are no annotations, so the description carries full responsibility for behavioral disclosure. It implies a read-only operation via 'List', but provides no details about authentication, pagination, sorting, data scope, or what 'basic information' includes.

  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, concise sentence with no filler. The action and resource appear first, making the purpose immediately scannable.

  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 parameterless list operation this is minimally adequate, but the phrase 'basic information' is vague and there is no output schema describing the returned fields. An agent cannot know exactly what data it will receive.

  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 empty schema is complete. The description does not need to add parameter-level meaning, and the baseline of 4 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 a specific action (list) on a specific resource (all created projects) and mentions 'basic information' as the scope. The plural 'all projects' differentiates this from the singular get_project sibling.

  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 given about when to use this tool versus get_project or the other siblings. There are no explicit conditions, exclusions, or alternative suggestions.

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

• generate_outlineA
  3.8/5.0
  Behavior3/5

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

  With no annotations, the description must carry behavioral disclosure, and it does state the core action of creating and saving. It does not explain side effects such as whether each call creates a fresh project, what the mutation requires (e.g., a Claude-generated outline with <page> tags), or what is returned. This is acceptable but not rich.

  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 short, front-loaded sentences with no filler; the primary action appears in the first clause. The second sentence is slightly vague ('proper formatting') but still earns its place by pointing the agent to the prompt.

  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 low-complexity tool whose parameters are fully documented in the schema, the description covers the basic workflow. However, with no annotations and no output schema, it would be stronger if it mentioned what happens after creation or pointed to get_project/list_all_projects for verification. The omission is a real but moderate gap.

  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 theme, outline, and referenceImage, including the full outline prompt. The tool description adds only a generic directive to use the built-in prompt, which is not new semantic information.

  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 opens with a precise action: 'Create a project and save the Xiaohongshu content outline generated by Claude.' This clearly identifies the outcome and distinguishes it from sibling tools such as update_outline and generate_images. No tautology or missing resource.

  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?

  'Create a project' establishes a clear context: use this when you need a new project with an outline, as opposed to updating an existing outline. It does not explicitly name alternatives or state when not to use the tool, so it just misses the top score.

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

• generate_imagesA
  3.9/5.0
  Behavior3/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 does reveal the built-in prompt, cover-first ordering, and target style, but it says nothing about side effects, persistence, overwriting behavior, or the potentially long-running/costly nature of image generation. This leaves the tool only partially transparent.

  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 short sentences with the core action front-loaded. The second sentence repeats 'generate images' but earns its place by specifying the built-in prompt and Xiaohongshu style, so the definition stays tight and scannable.

  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 only two parameters, no nested objects, and no output schema, the description is largely complete: it states scope, sequence, prompt source, and style. The main missing piece is what the agent should expect as a result, but schema coverage and sibling clarity keep this from being a major gap.

  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% for both parameters, so the baseline is 3. The description's cover-first clause adds an ordering nuance but does not explain how the optional pages array interacts with that ordering or with the built-in prompt, so it adds little real parameter semantics beyond the 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 names the exact action (generate images) and the resource (a project), and adds distinguishing details: cover-first ordering and Xiaohongshu style. This cleanly separates it from the outline and project siblings without needing to open the schema.

  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?

  It clearly implies when to choose this tool—when project images are needed—and gives explicit operational guidance: use the built-in prompt and generate the cover before other pages. It does not state exclusions or alternatives, but the sibling set makes those unnecessary.

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