iconfont-mcp

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

The description adds valuable behavioral context beyond annotations: it explains that the tool can optionally save to a file, describes the return format options (JSON vs markdown), and mentions the saved_to field. Annotations cover read/write status and idempotency, but the description provides practical implementation details that help the agent understand what to expect.

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

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

The description is well-structured with clear sections (purpose, args, returns, examples) and front-loads the core functionality. It's appropriately sized for a tool with 4 parameters, though the examples section could be slightly more concise. Every sentence serves a purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity, 4 parameters, and no output schema, the description provides good coverage: it explains the core functionality, parameter usage, return formats, and includes examples. The main gap is the lack of an explicit output schema, but the description compensates by documenting the return structure in the Returns section.

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

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

With 100% schema description coverage, the schema already documents all parameters thoroughly. The description adds minimal additional parameter semantics beyond the schema - it mentions icon_id comes 'from search results' and gives context for output_path usage, but doesn't provide significant value beyond what's already in the structured schema fields.

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

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

The description clearly states the specific action ('download SVG data'), resource ('icon from Iconfont'), and distinguishes it from siblings by focusing on downloading individual icons rather than searching or managing projects. The first sentence directly answers what the tool does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context about when to use this tool ('icon_id can be obtained from search results') and includes two helpful examples. However, it doesn't explicitly state when NOT to use it or name specific alternatives among the sibling tools (like iconfont_search_icons for finding icons first).

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