Server Quality Checklist

Tool Scores

• get-poemA
  3.7/5.0
  Behavior3/5

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

  Annotations declare readOnlyHint=true, and the description is consistent. However, no additional behavioral details are given (e.g., behavior if ID not found, or any constraints). Since annotations already cover the read-only nature, the description adds minimal extra transparency.

  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, short sentence that front-loads the purpose without extraneous words. It is concise and to the point, though it could include a bit more context about 'pplog'.

  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, read-only tool with one well-documented parameter, the description adequately conveys the core functionality. It does not elaborate on return values or error handling, but given the absence of an output schema and the tool's simplicity, the description is sufficient.

  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 has 100% coverage with description 'Poem ID' for the only parameter. The description does not add further meaning or format details; thus, it meets the baseline expectation without adding extra value.

  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 action 'Retrieves', the resource 'a poem', and the method 'by ID'. It effectively distinguishes from siblings: 'create-poem' is a write operation, 'search-poems' is a query, while this tool is a direct fetch by ID.

  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 use when you have a specific ID, but does not provide explicit guidance on when to use this tool versus the sibling 'search-poems', nor does it mention any prerequisites or context for appropriate use.

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

• search-poemsA
  4.2/5.0
  Behavior4/5

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

  Annotations declare readOnlyHint=true, and the description does not contradict. It adds behavioral traits such as advanced query syntax, date handling, and logical operators. However, it does not describe pagination or result format.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness3/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is lengthy due to thorough query syntax documentation. While front-loaded with purpose, the extensive examples could be condensed without losing essential information. It is informative but not maximally concise.

  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 no output schema, the description lacks details about the return structure of search results. It covers input thoroughly but leaves output unspecified. For a search tool, this is a notable gap.

  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: detailed query syntax, critical note about relative dates, and empty string behavior. This greatly aids the agent in constructing correct queries.

  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 verb 'Searches' and resource 'poems in pplog', and includes 'advanced query syntax support' which distinguishes it from sibling tools 'create-poem' and 'get-poem'.

  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 includes a critical note about relative date queries, implying when to use this tool for search. It also mentions that empty string returns all poems. However, it does not explicitly state when not to use it or compare to alternatives.

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

• create-poemA
  4.5/5.0
  Behavior4/5

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

  Adds specific behavioral detail beyond the destructiveHint annotation: posting hides the previous poem from readers. Does not specify if author can still access it, but still provides useful context.

  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, no fluff. All information is relevant and front-loaded. Every sentence serves a purpose.

  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 creation tool with one parameter and no output schema, the description fully covers purpose, parameter usage, and a key behavioral consequence. No gaps.

  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?

  Describes the content parameter's structure (first line is title, rest is body), adding meaning beyond the schema description. Schema coverage is 100%, so baseline 3, but the extra detail justifies 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 it creates a poem, defines it as a casual short note, and distinguishes from sibling tools (get-poem, search-poems) by being the creation action.

  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?

  Implied usage: use to create a poem, not to retrieve. Mentions side effect of hiding previous poem, but lacks explicit when-to-use vs alternatives, though context makes it clear.

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