Server Quality Checklist

Tool Scores

• get-igorC
  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 but fails to deliver. It doesn't indicate whether this is a read or write operation, what permissions might be required, what the response format might be, or any side effects. The description provides no behavioral context beyond the vague triggering condition, leaving the agent with minimal understanding of how the tool behaves.

  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 extremely concise - a single sentence with no wasted words. However, this conciseness comes at the cost of meaningful content. While technically efficient in terms of word count, the description is under-specified rather than optimally concise, which slightly reduces the score from a perfect 5.

  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 lack of annotations, no output schema, and a description that provides minimal functional information, the description is incomplete. While there's only one parameter with good schema coverage, the description fails to explain what the tool actually does, when to use it, or what behavior to expect. For even a simple tool, this level of documentation is inadequate.

  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 has 100% description coverage for its single parameter 'favor' (described as 'Requests for Igor'), so the schema does the heavy lifting. The tool description adds no additional parameter information beyond what's already in the schema. With high schema coverage and no parameters mentioned in the description, this meets the baseline expectation of 3.

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

  Purpose2/5

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

  The description 'When somebody asks for or mentions Igor' is tautological - it essentially restates the tool name 'get-igor' without specifying what the tool actually does. It doesn't explain what action is performed or what resource is accessed. The description lacks a clear verb+resource combination that defines the tool's function.

  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 minimal guidance - it suggests using the tool when someone 'asks for or mentions Igor,' but this is vague and doesn't establish clear usage criteria. There are no explicit when-to-use or when-not-to-use guidelines, no mention of prerequisites, and no alternatives since there are no sibling tools. The guidance is insufficient for an agent to make informed decisions about tool selection.

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