Server Quality Checklist

Tool Scores

• get_member_profileA
  4.1/5.0
  Behavior3/5

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

  With no annotations provided, the description must carry the full burden of behavioral disclosure. The verb 'Retrieves' implies a read-only operation, and the description lists the returned data, but it does not explicitly state side effects, error behavior (e.g., member not found), or any rate limits or authorization requirements. This is acceptable for a simple lookup but not fully 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 two sentences: the first fronts the core action and data scope, the second the usage context. It is concise, free of filler, and every word 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?

  The tool is simple—one parameter, no output schema, no annotations. The description adequately covers the purpose, the returned data fields, and the canonical use case. For such a low-complexity tool, this is complete enough for an AI agent to select and invoke correctly.

  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 provides 100% description coverage for the sole parameter, memberId, including its type and an example format. The description adds no additional parameter-specific semantics, so it does not go beyond what the schema already provides. The score is at the baseline of 3.

  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's function using the verb 'Retrieves' and specifies the resource ('a member profile') and key data fields (loyalty tier, partner, travel history). It strongly differentiates from siblings: get_recommendations focuses on recommendations, and list_members lists members, while this tool retrieves a single member's profile.

  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 recommends when to use the tool: 'Use this to understand who the member is before making recommendations.' This provides clear contextual guidance. It does not, however, explicitly mention when not to use it or name alternative tools, leaving room for a more thorough comparison.

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

• get_recommendationsA
  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 burden of disclosing behavior. It reveals that recommendations are filtered by partner rules including category exclusions and recommendation caps, and implies a dependency on get_member_profile. This adds meaningful context beyond the name, though it doesn't cover failure modes or exact return structure.

  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 sentences: the first states purpose and filters, the second gives a clear prerequisite. Both sentences are informative and free of fluff, making it maximally concise and well-structured.

  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 read-only tool, the description covers the core behavior (returns recommendations), key filtering details, and a required dependency. It doesn't describe the response format or error conditions, but given the absence of an output schema and the tool's simplicity, it's reasonably complete.

  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 fully describes the memberId parameter (100% coverage). The description adds no additional parameter-specific details, so it neither enhances nor detracts from the schema's clarity. Baseline of 3 is appropriate.

  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 returns personalized travel recommendations for a member, with the specific verb 'returns' and resource 'travel recommendations'. It also mentions filtering by partner rules, which distinguishes it from sibling tools like get_member_profile and list_members.

  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 instructs to call get_member_profile first, providing a clear prerequisite and ordering. However, it does not explicitly mention when not to use this tool or alternatives, though the clear resource distinction and naming make the usage context strong.

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

• list_membersA
  4.2/5.0
  Behavior3/5

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

  There are no annotations, so the description must fully disclose behavior. It states the tool returns all available members, implying a read-only operation with no side effects. Yet it does not mention response shape, pagination, or any access constraints, leaving some behavioral ambiguity.

  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 concise sentences that are front-loaded—the first sentence states the core action, the second gives an explicit use case. No unnecessary words or repetition.

  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 tool with no parameters and no output schema, this description covers the core functionality and a known use case. It could expand on the return format, but the simplicity of the tool makes this 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 input schema is empty (zero parameters) with 100% schema coverage. The description adds nothing about parameters, but since none exist, it is sufficient. Baseline score of 4 for zero parameters is appropriate.

  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 'Returns all available members in the system,' which is a specific action and resource. It distinguishes from sibling tools like get_member_profile and get_recommendations by focusing on the full member list rather than individual profiles or recommendations. The added note about discovering valid member IDs reinforces the tool's purpose.

  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 phrase 'Use this to discover valid member IDs' gives a clear context for when to call this tool. However, it does not explicitly contrast with sibling tools or state when not to use it, such as 'if you need a single member's details, use get_member_profile instead.'

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