Server Quality Checklist

Tool Scores

• add_taskB
  3.1/5.0
  Behavior2/5

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

  No annotations are provided, so the description must carry the full burden. It states 'Add a new task' but does not disclose permissions, idempotency, duplicate handling, or effects on existing tasks; the output schema exists but is not described in the text. This is a mutation tool with minimal behavioral disclosure.

  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 key verb/resource are front-loaded. It is appropriately brief for a simple tool, though it could include more context without becoming verbose.

  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?

  Given the trivial complexity and presence of an output schema, the description covers the basic purpose. However, with no annotations and no usage guidance, it leaves gaps around behavior and choice among sibling tools; it is minimally adequate.

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

  Parameters2/5

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

  Schema description coverage is 0%, and the description adds no meaning beyond the schema's 'task' string titled 'Task'. It does not explain expected format, length, or whether the task string includes status/priority; the single parameter's semantics are only obvious from its name.

  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 ('Add') and resource ('task'), clearly indicating the operation on the todo list. This differentiates it from siblings (complete_task, delete_task, list_tasks) by naming the create action.

  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 over alternatives; siblings are listed but no exclusions or context are mentioned. The description only states the action, leaving the agent to infer usage from the tool name.

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

• delete_taskA
  3.8/5.0
  Behavior2/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 states the action ('Delete') but does not disclose that this is a permanent, destructive operation or whether it requires any prerequisites or has irreversible consequences. The description is minimal and fails to add transparency beyond the action itself.

  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 a single, concise sentence that immediately states the action and parameter use. There is no wasted wording, and it is front-loaded with the verb 'Delete'.

  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?

  Given the tool's simplicity (one parameter, obvious action), the description is reasonably complete. It explains what the tool does and how to specify the target. However, it omits any details about return values or potential error cases, though an output schema exists that might cover that. For a straightforward delete, it is adequate.

  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 schema provides only the parameter type (integer) with no description (0% coverage). The description compensates by stating 'using its ID', clarifying that task_id is the identifier of the task to be deleted. This adds meaningful context to the parameter, making it clear how to populate it.

  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 action ('Delete a task') and the resource ('from the list'), using 'its ID' to specify the means. It is distinct from sibling tools like add_task, list_tasks, and complete_task, which perform different operations.

  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 usage is implied: you use this when you need to permanently remove a task. However, there is no explicit guidance on when to use it versus alternatives, and no mention of prerequisites or exclusions. It does not mislead, but it lacks explicit direction.

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

• complete_taskA
  4.2/5.0
  Behavior3/5

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

  With no annotations, the description carries the full burden. It states the mutation ('Mark as completed') but does not disclose side effects, idempotency, error behavior on invalid IDs, or prerequisites. Minimal but not misleading, so a low-average score is appropriate.

  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 a single, tightly written sentence that immediately conveys purpose and key parameter usage. No wasted words.

  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 an output schema, the description covers the core action. It omits details like required existence of the task or error handling, but given the simplicity and clear sibling context, it is reasonably complete.

  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 description clarifies that 'task_id' is an ID and also an index, giving practical meaning beyond the integer type. Although schema coverage is 0%, the description compensates sufficiently for the single parameter, though it could add more on valid ranges or required existence.

  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?

  Specific verb 'Mark' + resource 'task' + action 'completed' clearly states the tool's function. The parenthetical 'using its ID (index)' adds the key parameter context. It is easily distinguished from sibling tools like delete_task and add_task.

  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 clearly implies that the tool requires an existing task ID, which establishes when to use it. However, it does not explicitly mention when not to use it or suggest alternatives, but the sibling names make the distinctions obvious.

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

• list_tasksA
  4.3/5.0
  Behavior3/5

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

  There are no annotations, so the description carries the behavioral transparency burden. It accurately implies a read-only listing of all tasks, but provides no additional behavioral context such as ordering, pagination, or performance implications. For a zero-parameter list tool this is acceptable, though 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.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single, front-loaded sentence that expresses exactly what the tool does with no wasted words. It is appropriately concise for the tool's simplicity.

  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?

  This is a very simple zero-parameter tool with an output schema available. The description fully covers its externally visible behavior: it lists all tasks. Given the tool's simplicity and the presence of an output schema, no further contextual detail is required.

  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 parameters and schema description coverage is 100%. Since there are no parameters to explain, the description does not need to provide additional parameter semantics; 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 uses a specific verb ('list'), identifies the resource ('tasks'), and states the scope ('all tasks in the todo list'). It is clearly distinct from the mutating sibling tools complete_task, delete_task, and add_task.

  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 makes the use case clear: call this to view every task in the todo list. It does not explicitly mention when not to use it, but the distinction from mutating sibling tools is straightforward and unlikely to confuse an agent.

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