Server Quality Checklist

Tool Scores

• get_yield_poolsA
  3.5/5.0
  Behavior3/5

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

  No annotations are provided, so the description carries the full burden. It discloses that the tool fetches data (read operation) and returns specific fields, but lacks details on rate limits, authentication needs, error handling, or pagination. It adds basic context but misses key behavioral traits for an API call tool.

  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 well-structured and front-loaded with the main purpose, followed by return details and parameter explanations. It uses three concise sentences with no wasted words, efficiently conveying necessary information 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?

  Given no annotations, no output schema, and 2 parameters, the description is moderately complete. It covers purpose, parameters, and return fields, but lacks output structure details, error cases, or advanced usage context. It's adequate for basic use but has gaps for full agent understanding.

  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?

  With 0% schema description coverage, the description compensates by explaining both parameters ('chain' and 'project') with examples (e.g., 'Ethereum', 'lido'), clarifying their optional nature and usage. This adds meaningful semantics beyond the bare schema, though it doesn't cover all potential nuances like format constraints.

  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 ('Fetch DeFi yield pools') and resource ('from the yields.llama.fi API'), with optional filtering capabilities. It distinguishes the tool's function well, though without sibling tools, differentiation isn't applicable. The purpose is specific and actionable.

  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 usage through the optional filters ('optionally filtering by chain or project'), suggesting when to apply them. However, it lacks explicit guidance on when to use this tool versus alternatives, prerequisites, or exclusions. With no sibling tools, context is limited to implied filtering scenarios.

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