Server Quality Checklist

Tool Scores

• get_usage_detailsC
  2.9/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, but it only states the action without explaining side effects, authentication requirements, or whether results are cached or live. The presence of password and username parameters hints at auth needs, but the description itself does not disclose this or any other behavioral trait.

  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 with no wasted words. It immediately states what the tool does and scopes it to the current billing period, making it easy to parse quickly.

  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?

  The tool has no output schema and no annotations, so the description needs to explain the return format and any operational context. It does neither, leaving the agent uncertain about what 'detailed usage breakdown' contains, whether credentials are actually required, and how this relates to the account overview sibling. For a tool with optional auth parameters, this is a notable gap.

  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?

  Schema description coverage is 100%, so the schema already documents all three parameters. The description adds no extra parameter-level detail, such as format requirements or interactions between the optional credentials and the line parameter. Baseline 3 applies because the schema handles parameter documentation adequately.

  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 identifies a specific verb ('Get') and resource (T-Mobile data/call/text usage breakdown for the current billing period), so an agent can understand the tool's core function. It does not explicitly contrast with sibling tools like get_account_overview or pay_bill, but the resource is distinct enough that the purpose is unambiguous.

  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 such as get_account_overview. There is no mention of prerequisites, fallback options, or conditions that would make this the right choice. The usage context must be inferred entirely from the tool name and description.

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

• get_bill_historyB
  3.2/5.0
  Behavior2/5

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

  No annotations are provided, so the description alone must convey behavioral traits. 'View' signals a read-only operation, but the description does not disclose authentication requirements, that external T-Mobile credentials are used, login failure behavior, or any response/pagination characteristics.

  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 with no filler, repetition, or irrelevant detail. Every word earns its place.

  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?

  With no output schema and no annotations, the description leaves the agent without information about the return value shape, pagination/volume, or the authentication flow implied by the username/password parameters. For a three-parameter tool that accesses an external T-Mobile account, this is a meaningful gap.

  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 describes all three parameters (months, username, password) at 100% coverage, so the description does not need to add parameter details. The tool description itself adds no parameter meaning beyond the schema, matching the baseline.

  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 uses a specific verb ('View') and a clear resource ('past T-Mobile bills and payment history'), which tells the agent what the tool retrieves. It is distinguishable from siblings like pay_bill, but it does not explicitly call out sibling tools to reinforce the boundary.

  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 wording implies this is for read-only historical billing/payment access. It contrasts with pay_bill or get_usage_details, but there is no explicit statement of when to choose this tool or when an alternative is preferred.

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

• check_upgrade_eligibilityB
  3.3/5.0
  Behavior2/5

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

  With no annotations, the description carries the full burden, but it only says 'Check' and does not disclose what the tool returns, whether it makes an external network call, whether authentication is required despite optional credentials, or whether any state changes occur.

  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 with no filler. It immediately communicates the verb, target, and scope, making it easy to parse.

  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?

  For a simple read-style tool with fully optional, documented parameters, the description is adequate but has gaps: no output schema and no mention of what the response looks like or what conditions might affect eligibility. It is serviceable but not rich enough for full autonomy in ambiguous situations.

  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?

  Schema coverage is 100%, so the parameters are already well documented in the input schema. The description adds the context that eligibility applies to 'lines on the account,' but it does not add meaning beyond the schema's parameter descriptions.

  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 ('Check') and a clear resource ('T-Mobile device upgrade eligibility for lines on the account'). It is distinct from the sibling tools, which cover overview, usage, payments, and billing, though it does not explicitly contrast itself with them.

  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 intended use case is implied by the description: call this when upgrade eligibility is needed. However, there is no explicit guidance about when not to use it, prerequisites for authentication, or how it relates to the sibling account tools.

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

• get_account_overviewB
  3.4/5.0
  Behavior3/5

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

  Without annotations, the description carries the burden of behavioral disclosure. It states authentication is required ('Requires login credentials'), which is useful. However, it doesn't disclose side effects, read-only nature, external login redirect behavior, session handling, or errors with bad credentials.

  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 plus a short auth note, which is efficient and front-loads the main purpose. It earns its place without redundancy.

  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?

  For a read-oriented overview tool with 2 simple params and no output schema, the description is reasonably adequate. Missing details: whether usage summary is current-month, whether return values include recent charges, and what happens if credentials are missing. Could be more complete given the auth-sensitive nature.

  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 schema already describes both parameters well with 100% coverage. The description adds the requirement that they are login-related but doesn't clarify precedence if both username and env var are set, or format expectations beyond the schema.

  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 identifies the tool as retrieving a T-Mobile account overview with plan, balance, and usage summary. The verb 'Get' plus the resource 'T-Mobile account overview' gives a specific purpose, though it doesn't explicitly distinguish it from get_usage_details, which could theoretically overlap.

  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 this is the account-level overview tool, and sibling tools like get_bill_history or get_usage_details exist for more specific data. However, there's no explicit 'when to use this vs. alternatives' guidance or exclusions stated.

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

• pay_billA
  3.8/5.0
  Behavior3/5

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

  With no annotations, the description must disclose behavior itself, and it does add a useful trait: the payment is not confirmed yet, only review details are returned. However, it does not clarify what happens after review, whether this call actually charges the account, or if a separate confirmation step exists. This leaves meaningful ambiguity for a financial 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?

  Two sentences with zero filler: the first states the action and target, the second provides the key return behavior. 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.

  Completeness2/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  For a financial action with 4 optional parameters and no output schema, the description is under-specified. It introduces a review-before-confirmation flow but doesn't explain how to proceed after review, how optional parameters interact, or what a successful response looks like. An agent would be uncertain about the full workflow.

  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?

  Schema description coverage is 100% for all 4 parameters, so the baseline is 3. The description adds no parameter-specific meaning beyond the schema, but it doesn't need to since each parameter is already documented. No gaps to compensate for.

  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 ('Initiate') and resource ('one-time bill payment for T-Mobile account'), clearly distinguishing it from sibling read-only tools like get_usage_details and check_upgrade_eligibility. The added detail about returning payment details for review further clarifies its unique role.

  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 explicit: this is the tool for initiating a payment, in contrast to the sibling tools that all retrieve information. It doesn't explicitly name alternatives or exclusions, but the intended context is clear enough for an agent to select it over the getters.

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