Server Quality Checklist

Tool Scores

• postA
  3.9/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 convey behavioral traits. It states 'Publish a post' implying a write operation, but does not disclose aspects like whether the operation is synchronous, error handling, rate limits, or permissions needed. The minimal disclosure leaves the agent with uncertainties.

  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 long, front-loading the core action and immediately following with optional parameters and targeting rules. Every word contributes meaning, with no redundancy or filler.

  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 tool has 5 parameters (one required), no output schema, and no annotations, the description covers the basics of usage but lacks information about the return value or error scenarios. It is adequate for a standard tool but could be improved with a brief note on what the response looks like.

  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?

  Schema coverage is 100% with well-described parameters. The description adds value by explaining how to use 'platform' versus 'account_id' and gives concrete examples for 'settings' (e.g., reddit {subreddit, title}), which goes beyond the schema's definition.

  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 'Publish a post to a connected account' with specific verb and resource. It also differentiates from sibling tools (connect_account, get_analytics, list_accounts, list_platforms) which are not posting tools. Additional details like media and per-platform settings further clarify scope.

  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 guidance on targeting an account by account_id or by platform when only one account is connected. It also gives an example of per-platform settings with reddit {subreddit, title}. However, it does not explicitly exclude scenarios or mention alternatives beyond the given options.

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

• list_platformsA
  4.2/5.0
  Behavior4/5

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

  No annotations provided, so the description carries full behavioral burden. It adequately describes what the tool returns (platform list with details) and implies a read-only operation. However, it does not explicitly mention rate limits, authentication needs, or safety.

  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?

  Single sentence that packs all relevant detail. It is front-loaded with 'List every supported social platform' and efficiently covers key aspects. Slightly wordy but clear.

  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?

  For a simple tool with no parameters and no output schema, the description fully explains the purpose and output details (status, connection, credentials, analytics). It provides sufficient context for an agent to understand what to expect.

  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?

  No parameters, so schema coverage is 100%. Baseline is 4. The description does not need to add parameter information.

  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 lists every supported social platform with specific attributes (status, connection, credentials, analytics). It distinguishes itself from siblings like 'list_accounts' which likely lists user accounts.

  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?

  No explicit guidance on when to use or not use this tool versus alternatives. The use case is implied by the description, but there is no mention of preconditions or exclusions.

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

• list_accountsA
  4.5/5.0
  Behavior4/5

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

  No annotations are provided, so the description bears full responsibility. The term 'list' strongly implies a read-only, non-destructive operation. However, it does not explicitly confirm no side effects or mention authentication/rate limits, which would elevate transparency.

  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?

  Single sentence, front-loaded with action, efficiently conveys purpose, output, and usage hint. No unnecessary words.

  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?

  Completely covers the tool's purpose, output, and cross-reference to sibling tools. Given the tool's simplicity (0 parameters, no output schema), no additional information is needed.

  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 tool has zero parameters and schema_description_coverage is 100% (trivially). With no parameters, the description adds value by listing output fields, which is appropriate. Baseline for 0 params is 4.

  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?

  Clearly states the action 'list', the resource 'social accounts you have connected', and specifies the output fields (platform, handle, account id). Distinguishes from siblings like connect_account (add) and post (create content).

  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?

  Provides usage guidance by telling the agent to use the account id from this tool in 'post / get_analytics'. Implicitly indicates when to use (before posting/analytics) but does not explicitly state when not to use or prerequisites.

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

• connect_accountA
  4.6/5.0
  Behavior4/5

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

  Given no annotations, the description carries full burden. It discloses that OAuth returns a URL, credential connects immediately, and hints at dynamic field requirements. It does not mention side effects or permissions, but adequately describes the behavior.

  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?

  Three sentences, front-loaded with purpose, no wasted words. Well-structured to convey key information quickly.

  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?

  No output schema exists, but the description covers what to expect: URL for OAuth, immediate connection for credential. It addresses all aspects of tool usage given its complexity (2 params, nested object). Complete and self-contained.

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

  Parameters5/5

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

  Schema coverage is 100% and the description adds significant meaning beyond the schema: it explains the 'fields' parameter as an object with platform-specific examples (bluesky, nostr) and clarifies the 'platform' parameter. This helps the agent understand expected input.

  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 connects social accounts, distinguishes between OAuth and credential platforms, and explains the behavior. It uses specific verbs and resources, and is distinct from sibling tools like list_accounts and post.

  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?

  Provides explicit when-to-use guidance: connect an account. Explains how to use for OAuth vs credential platforms and advises calling with just a platform to see required fields. Lacks explicit when-not-to-use or alternatives, but the context is clear.

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

• get_analyticsA
  4.6/5.0
  Behavior5/5

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

  Discloses critical behavior: returns only metrics the platform provides, never fake zeros. No annotations exist, so description carries full burden and meets it.

  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 concise sentences covering purpose, behavior, and usage. No redundant information.

  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?

  No output schema but explains return semantics. Provides sibling context. Lacks details on error handling or pagination but adequate for a read tool.

  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?

  Adds context beyond schema: explains post_id origin, when to use platform vs account_id, and account_id source. Schema coverage is 100% but description enhances meaning.

  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?

  Clearly states verb 'read' and resource 'normalized analytics for one published post'. Distinct from sibling tools like 'post' and 'list_accounts'.

  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?

  Specifies targeting by account_id or platform with post_id from 'post' tool. Lacks explicit when-not-to-use but sufficient for typical use.

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