Server Quality Checklist

Tool Scores

• strip_image_metadataA
  4/5.0
  Behavior4/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 clearly states the destructive effect (removes metadata), supported formats, the lack of authentication requirements, and the output as a downloadable cleaned image. Minor gaps remain, such as whether the original URL image is modified or just the returned copy, but the core behavior is transparent.

  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 three concise sentences with no wasted words. The core action and metadata types are front-loaded, followed by format support, access requirements, and output behavior. Every sentence provides useful information.

  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 tool with no output schema, the description covers input format, supported file types, authentication needs, and the returned result. It does not specify output file format or size limits, but these are not necessary for basic correct 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 description coverage is 100%, with image_url already documented as 'URL of the image to strip metadata from.' The description does not add new parameter-level detail, but the schema alone sufficiently explains the only parameter, so the baseline 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 uses a specific verb ('Removes') with a clear resource ('metadata from images') and enumerates the exact metadata types (C2PA, EXIF, XMP, ICC, and all other metadata). It also lists supported formats, making it unmistakably distinct from the sibling tool rewrite_text.

  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: whenever an image needs its metadata removed. It provides supporting context like supported formats and no API key requirement, but it does not explicitly state when not to use it or compare it against alternatives.

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

• rewrite_textA
  4.2/5.0
  Behavior4/5

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

  With no annotations, the description carries the full disclosure burden. It reveals important behavioral traits: rewriting happens at sentence and clause level, meaning/facts/numbers/names/code are preserved, and the goal is to evade Claude content detection. This goes beyond a generic 'rewrite' and gives the agent a realistic picture of the transformation, though it stops short of describing output format or failure modes.

  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?

  Two sentences with no filler. The first sentence front-loads exactly what the tool does and what it preserves, while the second sentence gives a concrete use case. 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 single-parameter text transformation tool, the description covers the purpose, the transformation behavior, and the intended use case. It does not explicitly state that the output is the rewritten text, but this is implied by 'rewrites a passage' and the use-case sentence. Minor gap, but overall sufficient for correct 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?

  The input schema already describes the only parameter, text, including the upper bound of ~30,000 characters and the suggestion to split longer documents. The description adds no additional parameter-level meaning, so the baseline of 3 applies because schema coverage is 100%.

  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 verb ('rewrites'), a precise resource ('a passage of text'), and the level of operation ('sentence and clause level'), plus the intended effect: removing the statistical pattern that Claude content detectors flag. This is clearly distinguished from the sibling tool strip_image_metadata, which operates on images rather than text.

  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 tells the agent when to use this tool: 'Use this to clean text copied from Claude, Claude Code, or the Claude API before publishing.' It does not explicitly state when not to use it or name alternatives, but the sibling tool is obviously about image metadata, so the usage boundary is clear enough without an explicit exclusion.

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