Server Quality Checklist

Tool Scores

• read_sessionB
  3.2/5.0
  Behavior3/5

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

  Annotations already declare the operation read-only, idempotent, and non-destructive; the description reinforces this by noting the original session is preserved. It adds a small amount of useful context about returning display text, but no additional behavioral details such as formatting, truncation, or side effects.

  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 short sentences deliver the core action and a safety guarantee with no filler. The most important information is front-loaded and every sentence earns its place.

  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 has no output schema, and the description gives only a minimal hint of return content (display text). Required parameters and defaults are left to the schema, while the description does not explain how maxChars or maxMessages affect the result or when this tool should be chosen over sibling tools.

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

  Parameters1/5

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

  Schema description coverage is only 40%, and the description contributes no parameter-level meaning. Parameters like maxChars, maxMessages, and sessionId remain unexplained by both the schema and the description, so the low coverage is not compensated.

  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 states a specific action (reads display text) on a specific resource (the selected session) and adds a preservation guarantee. It is clear enough to be distinguished from list_sessions and prepare_handoff, though it does not explicitly name or contrast the 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 phrasing implies the tool is used when an agent needs the rendered text of a specific session, but no explicit when-to-use, when-not-to-use, or alternative conditions are provided. It does not explain how this relates to list_sessions or prepare_handoff.

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

• list_sessionsB
  3.4/5.0
  Behavior3/5

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

  Annotations already declare this tool read-only and idempotent. The description adds useful context by specifying it targets local sessions of the same project and is a precursor to fetching body text, but it does not disclose return format, pagination behavior, or how session selection works.

  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 focused sentence that front-loads the tool's purpose and immediately states its intended position in the workflow. There is no redundancy or filler.

  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?

  For a tool with four parameters, no output schema, and a need to guide an agent through the selection-to-read flow, this description is too thin. It does not explain what the tool returns, how to choose a session, or how the result feeds into read_session, so an agent may struggle to invoke it correctly.

  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 coverage is only 50%, and the description adds no parameter-level meaning beyond what the schema already provides. The 'same project' phrasing loosely maps to projectPath, but limit and offset remain undocumented in both schema and description, so the description does not compensate for the gap.

  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 states a specific verb and resource: it finds and selects local sessions for the same project. It also adds sequencing context ('use before fetching the body'), which helps distinguish it from read_session, though it does not explicitly differentiate it from prepare_handoff.

  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 gives clear usage context: it should be used before fetching session body content. However, it does not state when not to use it or explicitly name alternatives, leaving some inference to the agent.

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

• prepare_handoffA
  3.7/5.0
  Behavior4/5

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

  Annotations already set readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds meaningful behavioral context by clarifying the tool only imports reference context and does not grant execution rights for the original instructions. This goes beyond the annotations without contradicting them.

  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 two short sentences with no filler. The main action is front-loaded, and the safety caveat about original instructions earns its place. This is concise and well-structured.

  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 description covers core purpose and a key limitation, but with 5 parameters, no output schema, and sibling tools, it leaves gaps around parameter semantics and when to choose this tool versus read_session/list_sessions. It is minimally adequate but not fully complete.

  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 only 40%, and the description does not compensate by explaining parameters like sessionId, maxChars, or maxMessages. It implicitly references the selected session and current tool, but it leaves important parameter semantics unexplained.

  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 clearly states the verb and resource: it imports a selected session into the current tool as reference context for continuation. It also distinguishes itself from executing original instructions, but it does not explicitly differentiate itself from the sibling tools read_session or list_sessions.

  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 clear usage context: use this when you need to bring a prior session into the current tool as reference context. It also warns that original instructions are not execution authorization, which is a useful when-not. However, it does not explicitly mention alternatives or when to prefer read_session/list_sessions.

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