Server Quality Checklist

Tool Scores

• query_dataC
  2.4/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 'Query data' which implies a read operation, but doesn't clarify if it's safe (non-destructive), requires authentication, has rate limits, or what the output looks like (e.g., format, pagination). This leaves significant gaps for a tool with three parameters.

  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, efficient sentence with zero waste. It's appropriately sized and front-loaded, though this conciseness comes at the cost of detail, making it under-specified rather than verbose.

  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?

  Given the complexity (3 parameters, nested objects, no output schema, and no annotations), the description is incomplete. It doesn't cover parameter usage, behavioral traits, or output expectations, leaving the agent with insufficient information to use the tool effectively beyond a basic guess.

  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 0%, so the schema provides no parameter details. The description adds no meaning beyond the tool name—it doesn't explain what 'table', 'select', or 'filters' parameters do, their expected formats, or how they interact. For three undocumented parameters, this is inadequate.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose3/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description 'Query data from Supabase' states the action (query) and target (Supabase data), which is clear but vague. It doesn't specify what type of query (e.g., SELECT with filters) or distinguish it from siblings like delete_record, insert_record, update_record beyond the generic 'query' verb.

  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 provided on when to use this tool versus alternatives. The description lacks context on prerequisites, such as when querying is appropriate compared to insert_record or update_record, or any constraints like table permissions or data availability.

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

• delete_recordC
  2.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. While 'Delete' implies a destructive mutation, the description doesn't specify whether this operation is irreversible, what permissions are required, or how errors are handled. It mentions Supabase but doesn't explain authentication or rate limits.

  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, efficient sentence with zero waste. It's appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration.

  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 destructive mutation tool with 2 undocumented parameters, 0% schema coverage, no annotations, and no output schema, the description is inadequate. It doesn't address critical aspects like safety warnings, parameter usage, or expected outcomes, leaving the agent poorly equipped to use this tool 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 description coverage is 0%, so the description must compensate but fails to do so. It doesn't explain what 'table' and 'filters' parameters mean, their expected formats, or provide examples. For a tool with 2 required parameters and nested objects, this leaves significant gaps in understanding.

  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 action ('Delete') and resource ('a record from Supabase'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from its sibling 'update_record' in terms of destructive nature or mention that 'query_data' might be a safer alternative for read operations.

  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 provided about when to use this tool versus alternatives like 'insert_record' or 'update_record'. The description lacks context about prerequisites, permissions needed, or warnings about irreversible deletion, which is critical for a destructive operation.

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

• insert_recordC
  2.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 full burden for behavioral disclosure. 'Insert' implies a write/mutation operation, but the description doesn't specify permissions needed, whether the operation is idempotent, what happens on conflicts, or what the response contains. This leaves significant behavioral gaps for a database mutation tool.

  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 at just 5 words, with zero wasted language. It's front-loaded with the core action and target, making it immediately understandable despite its brevity.

  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 database mutation tool with 2 parameters, 0% schema coverage, no annotations, and no output schema, the description is inadequate. It doesn't explain what constitutes a valid 'record', how 'data' should be structured, what happens on success/failure, or how this differs from sibling tools.

  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?

  With 0% schema description coverage for both parameters, the description provides no information about what 'table' and 'data' mean, their expected formats, or constraints. The description doesn't compensate for the complete lack of parameter documentation in 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 states the action ('insert') and target resource ('record into Supabase'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'update_record' beyond the basic verb difference, missing an opportunity to clarify when to use insert versus update.

  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 like 'update_record' or 'delete_record'. There's no mention of prerequisites, appropriate contexts, or exclusions, leaving the agent to infer usage from the tool name alone.

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

• update_recordC
  2.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 full burden but only states the basic operation. It doesn't disclose behavioral traits like required permissions, whether updates are reversible, rate limits, error handling, or what happens to existing data not mentioned in 'data' parameter. For a mutation tool with zero annotation coverage, this is inadequate.

  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, efficient sentence with zero wasted words. It's appropriately sized and front-loaded with the core purpose.

  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 3-parameter mutation tool with no annotations, 0% schema description coverage, and no output schema, the description is incomplete. It doesn't address parameter meanings, behavioral implications, or usage context, leaving significant gaps for agent understanding.

  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%, so the description must compensate but adds no parameter information. It doesn't explain what 'table', 'filters', or 'data' represent, their expected formats, or how they interact. This leaves all 3 parameters undocumented beyond their schema types.

  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 action ('Update') and target ('a record in Supabase'), providing specific verb+resource. However, it doesn't differentiate from sibling tools like 'insert_record' or 'delete_record' beyond the basic operation type.

  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 provided about when to use this tool versus alternatives like 'insert_record' (for new records) or 'delete_record' (for removal). The description lacks context about prerequisites, appropriate scenarios, or exclusions.

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