Server Quality Checklist

Tool Scores

• add_noteA
  4.1/5.0
  Behavior3/5

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

  Because no annotations are provided, the description carries the burden of explaining behavior. It clarifies that notes are appended rather than overwritten and that confirmation is returned. However, it does not mention what happens if the notes file does not exist or whether any permissions are required.

  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 short, starts with a one-sentence summary, and then cleanly lists the parameter and return value. It avoids unnecessary detail, though the Returns section is slightly redundant with the output schema.

  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 one-parameter append operation, the description covers the action, the parameter semantics, and the return value. It does not specify file location or creation behavior, but those details are not essential for an agent to correctly invoke this simple tool.

  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?

  Schema description coverage is 0%, so the description must add meaning beyond the bare parameter name. It does this by defining message as 'the note to append', which clarifies exactly how the parameter is used. For a single simple string parameter, this is sufficient.

  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 opening line uses a specific verb ('Append') and a concrete resource ('the notes file'), which makes the tool's purpose immediately clear. The append-versus-read contrast is enough to distinguish it from the sibling tool read_notes.

  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 establishes a clear context: this tool is for adding new content to the notes file. Although it does not explicitly say 'use read_notes for reading', the action of appending versus reading makes the appropriate usage obvious.

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

• read_notesA
  4.3/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 and does a good job: it discloses the return type (str), the ordering (newest last), and the no-notes fallback message. This goes beyond a simple one-liner and gives the agent useful behavioral expectations.

  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 short and front-loaded with the core purpose. The Returns section adds essential details without any fluff. Every sentence earns its place.

  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?

  For a simple, parameterless read tool, the description fully covers what an agent needs to know: what it does, what it returns, ordering, and the empty case. There is no missing information that would prevent correct 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, so the schema already covers everything. The description sensibly focuses on return behavior rather than parameters, which is appropriate for a parameterless tool.

  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 and resource ('Read every stored note') and is unambiguously distinct from the only sibling, add_note, which writes instead of reads. Even without looking at the schema, an agent knows exactly what the tool does.

  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 the agent needs to read all stored notes. However, there is no explicit guidance about when not to use it or a contrast with the sibling add_note, so the usage context is only implied rather than clearly stated.

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