IT Tools MCP Server

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

No annotations are provided, so the description carries full burden. It mentions 'supports 295+ fonts' which adds useful context about capabilities, but doesn't disclose behavioral traits like whether this is a read-only operation, if it has rate limits, what happens with invalid inputs, or the format of the output (ASCII text string). For a tool with no annotation coverage, this leaves significant gaps in understanding its behavior.

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 perfectly concise: two sentences with zero waste. The first sentence states the core purpose, the second provides an example and key capability (font support). Every element earns its place, and it's front-loaded with the essential information.

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 2 parameters with 100% schema coverage but no annotations and no output schema, the description is adequate but incomplete. It covers the basic purpose and hints at capabilities, but doesn't address output format, error behavior, or operational constraints. For a simple transformation tool, this might be minimally viable, but the lack of output information is a notable gap.

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?

Schema description coverage is 100%, with both parameters well-documented in the schema. The description adds minimal value beyond the schema: it mentions 'figlet fonts' and '295+ fonts' which reinforces the font parameter context, and provides an example that illustrates the text parameter usage. However, it doesn't add significant semantic details beyond what the schema already provides.

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 tool's purpose: 'Generate ASCII art text using figlet fonts' with a specific example. It distinguishes from sibling tools like 'convert_text_to_binary' or 'capitalize_text' by focusing on visual text art rather than format conversion or case changes. However, it doesn't explicitly differentiate from all siblings (e.g., 'generate_qr_code' also creates visual representations).

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 implies usage context through the example and font support mention, suggesting this is for decorative text generation. It doesn't provide explicit when-to-use guidance versus alternatives like 'generate_qr_code' for different visual outputs or text formatting tools. The 'Use "standard" if unsure' hint offers some practical advice but lacks comprehensive alternatives or exclusions.

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