Server Quality Checklist

Tool Scores

• get_embed_codeB
  3.3/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 disclosing behavior. It only states the high-level function and does not mention any side effects (none likely), permissions, or specifics about the output (e.g., whether it is a snippet or full HTML document). The description simply restates the action without deeper 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?

  The description is a single sentence of 16 words, front-loaded with the core action and formats. It is highly concise and contains no fluff, effectively capturing the tool's purpose.

  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 7 parameters, 3 required, and no output schema, the description is minimal. It does not explain the workflow context (e.g., that family, style, and index come from previous search results) or what the returned embed code looks like. This makes it viable but lacking depth for a tool with this many parameters.

  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 description coverage is 100%, so the baseline is 3. The description adds no additional parameter semantics beyond what the schema already provides. It does not explain relationships between parameters (e.g., that 'index' comes from search results), but the schema itself covers that detail.

  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's action ('Generate ready-to-use embed code') and the resource ('Lordicon icon'), with specific output formats ('HTML, React, or web component format'). This distinguishes it from sibling tools like list_families, search_icons, and get_icon_preview, which serve different purposes.

  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. It does not mention that it should be used after searching for an icon, nor does it exclude any scenarios. The sibling tool names imply a workflow, but the description itself does not connect to them.

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

• get_icon_previewA
  3.5/5.0
  Behavior3/5

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

  With no annotations provided, the description must carry the burden of behavioral disclosure. It does state the return type ('embedded SVG image'), which is useful, but it does not explicitly confirm the operation is read-only or mention any side effects, limitations, or error conditions. The phrase 'Get a visual preview' implies safety but leaves ambiguity.

  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 exactly two sentences, front-loaded with the core purpose and followed by the return format. Every word contributes value; there is 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?

  The tool has 4 parameters and no output schema, so the description should ideally explain how parameters relate and what 'preview' entails. It covers the return format (SVG image) but lacks usage guidance, behavioral caveats, or any note about the source of the index. This makes it partially complete but with clear gaps in context.

  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 already describes all 4 parameters with full coverage. The description adds no extra meaning about parameter relationships, formats, or how to use the index from search results. Since schema coverage is 100%, the baseline of 3 is appropriate.

  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's function: 'Get a visual preview of a specific Lordicon icon' and specifies the return format as 'an embedded SVG image'. This verb+resource phrasing distinguishes it from siblings like list_families and search_icons, and even from get_embed_code which presumably returns code rather than a preview.

  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 compared to alternatives like get_embed_code. The description only explains what the tool does, not when it should be preferred or how it differs in use cases. There is no mention of prerequisites or exclusions, so the agent gets no contextual direction.

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

• search_iconsA
  3.5/5.0
  Behavior2/5

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

  With no annotations, the description must carry the full burden for disclosing behavior. It only mentions what is returned, but says nothing about whether this is a safe read-only operation, pagination behavior, rate limits, or any quirks. This is a significant transparency gap for an unannotated 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 a single, front-loaded sentence that communicates the core action and return value. Every word earns its place, 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?

  Even though the schema covers all parameters, there is no output schema and no annotations. The description gives a high-level list of returned fields but does not explain pagination, the meaning of 'indices', or how output is structured. For a search tool with 6 parameters and no output schema, this is minimally sufficient but leaves room for clarification.

  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 all 6 parameters, so the description doesn't need to add parameter details. The description's mention of 'keyword', 'families', and 'styles' loosely aligns with the query, family, and style parameters, but adds no new semantic information beyond what the schema already provides.

  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 ('Search') and resource ('Lordicon icons by keyword'), and differentiates from siblings by focusing on search rather than listing families or getting previews/embed codes. It also specifies return types (names, families, styles, indices), making the purpose unambiguous.

  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 phrase 'for use with other tools' implies it is a discovery step before using other tools, but it does not explicitly specify when to use this tool versus the siblings like list_families or get_icon_preview. No exclusions or alternative recommendations are given, so guidance is only implied.

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

• list_familiesA
  3.8/5.0
  Behavior3/5

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

  With no annotations, the description carries the burden of behavioral disclosure. It discloses that the tool returns a comprehensive list with counts, which is useful. However, it does not mention whether this is a read-only operation (though implied), any response format, pagination, or API-specific behaviors. For a simple list tool this is adequate but not rich.

  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?

  A single, front-loaded sentence that conveys the core functionality without any redundancy. Every word earns its place, making it highly concise and well-structured.

  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 tool with no parameters, no annotations, and no output schema, the description is suitably complete for a simple list operation. It explains what is returned (families, styles, counts), and the lack of further details is acceptable given the tool's simplicity. It could optionally mention the purpose relative to siblings, but that would be enhancement rather than necessity.

  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 no parameters, so the schema is complete (100% coverage). The description naturally adds no parameter semantics because none exist, but it does clarify that the output includes families, styles, and counts, which aligns with the zero-parameter baseline.

  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 uses a specific verb ('List') and resource ('all Lordicon icon families and their styles with icon counts'), clearly distinguishing this tool from siblings like search_icons or get_embed_code. It states exactly what is returned, making the purpose unmistakable.

  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. It does not mention any exclusions, prerequisites, or scenarios where another sibling tool might be preferred. The context of siblings exists but the description does not acknowledge them.

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