Server Quality Checklist

Tool Scores

• delete_noteB
  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 full responsibility for behavioral disclosure. It states 'Delete a note by ID' but does not mention that deletion is permanent, potential side effects, error conditions (e.g., invalid ID), or any required permissions. This is a meaningful 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, with one clear action sentence and a parameter definition. Every word earns its place, and the structure is front-loaded. No redundant 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 single-parameter delete tool, the description covers the core operation and parameter adequately. The presence of an output schema reduces the need to describe return values. However, the lack of behavioral context (e.g., permanence, error handling) prevents a perfect score, but given the simplicity of the tool, this is acceptable.

  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 only lists note_id as a required string. The description adds 'The unique identifier of the note to delete', which clarifies the parameter's role and uniqueness. However, this is minimal and does not compensate fully for the 0% schema description coverage; the semantic addition is limited.

  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 'Delete a note by ID', which is a specific verb ('Delete') and resource ('note'), and uses the identifier parameter. This clearly distinguishes it from sibling tools like list_notes, get_note, create_note, and update_note.

  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. It does not mention exclusions, prerequisites, or context for use. The action is obviously for deletion, but no explicit usage guidance is offered.

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

• get_noteA
  3.6/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. It only mentions 'full content' and gives an example ID, but does not disclose error behavior, authentication requirements, or whether the note might be trashed or inaccessible. Minimal behavioral context.

  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 and front-loaded with the purpose. The Args block is somewhat redundant with the schema, but it does not waste words and every component contributes to clarity.

  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 one parameter and an output schema exists, so return format is covered. However, the description lacks any note about behavior on missing IDs, access scopes, or pagination, leaving some contextual gaps for an agent to handle.

  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?

  Although the schema only defines note_id as a string, the description adds an Args block defining it as 'the unique identifier of the note' and provides an example. This adds meaning beyond the bare schema, even though schema coverage is 0% by itself.

  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 'Get a specific note by ID with full content', with a specific verb and resource. It distinguishes from sibling tools like list_notes (which implies listing multiple notes) by emphasizing 'specific note by ID'.

  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?

  Usage is implied: use when you have a note ID and need full content. However, it does not explicitly mention when not to use it or directly reference alternatives like list_notes for browsing notes, leaving differentiation to inference.

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

• update_noteA
  4/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 burden of behavioral disclosure. It does disclose a non-obvious behavior: 'The note title is automatically re-extracted from the first H1 heading.' This adds value beyond the basic update action. However, it does not mention potential side effects, error behaviors, or permission requirements, leaving some gaps.

  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 compact and well-structured: a one-sentence purpose, a notable behavioral note, and a clear Args list. Every line earns its place, and the essential information is front-loaded. No redundancy or fluff.

  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?

  The description covers the core purpose, key behavioral nuance, and parameter semantics. Since an output schema exists, the description need not explain return values. It could benefit from addressing edge cases like invalid note_id or whether content replaces or merges, but overall it provides sufficient context for a simple update operation.

  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 zero descriptions for its parameters, so the description compensates by providing explicit explanations: 'note_id: The unique identifier of the note to update' and 'content: New markdown content for the note.' This clarifies the meaning and role of each parameter effectively, though it could add more detail about content format or constraints.

  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 'Update an existing note's content,' which specifies the verb (update), resource (note), and scope (content). This distinguishes it from sibling tools like create, delete, list, and get, making the 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 phrase 'existing note' implies this tool is for notes that already exist, suggesting a contrast with create_note. However, there is no explicit guidance on when to use this versus alternatives, nor any exclusion criteria. The usage context is clear from the name and first sentence but not elaborated.

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

• create_noteA
  4.5/5.0
  Behavior4/5

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

  The description discloses a key behavioral trait beyond the schema: it automatically derives the title from the first H1 heading. It also clarifies that content is in markdown format. With no annotations available, this adds necessary transparency about how the tool processes input, though it doesn't cover edge cases like missing H1 or output behavior.

  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 only three sentences, front-loading the core purpose and then providing the necessary detail about title extraction. It avoids redundancy and stays tightly focused on the essential information for correct use.

  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 create tool, the description covers the primary purpose and the most critical behavior (title extraction). The presence of an output schema covers return values. However, it doesn't mention what happens if the content lacks an H1 heading or other edge cases, which could be relevant for the agent.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters5/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  The schema provides only a string property named 'content' with no description (0% coverage). The description explains that content is markdown and should start with '# Title', adding essential semantic meaning that the schema lacks. This fully compensates for the schema's lack of parameter documentation.

  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 'Create a new note with markdown content,' giving a specific verb, resource, and content format. This distinguishes it from sibling tools like list_notes, get_note, update_note, and delete_note.

  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 an implicit usage context (when creating a new note) and adds an important operational guideline: the title is automatically extracted from the first H1 heading, so content should start with '# Title'. While it doesn't explicitly name alternative tools, the guidance prevents misuse and clarifies the expected content structure.

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

• list_notesA
  4.7/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 burden. It discloses that only metadata is returned (no content) and that it is scoped to the authenticated user. It does not mention pagination or ordering, but for a simple list operation this is reasonably 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?

  Two concise sentences immediately state the action and the key limitation (no content), with a forward pointer to the alternative. No wasted words.

  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 zero-parameter list tool with an output schema, the description is complete: it explains what is returned, the scope, and directs to get_note for full content. Nothing critical is missing.

  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 fully covers parameter semantics (100% coverage). The baseline for 0 parameters is 4; the description adds no parameter info because none is needed.

  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 all notes for the authenticated user, with a specific verb ('List') and resource ('notes'). It distinguishes itself from sibling get_note by explicitly noting it returns metadata without content.

  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?

  The description explicitly instructs to use get_note for full content, providing an alternative and clarifying when this tool is appropriate (listing metadata). This meets the 'explicit when/when-not/alternatives' criterion.

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