generate_card_image

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

With no annotations provided, the description carries full burden for behavioral disclosure. While '转换为知识卡片图片' (convert to knowledge card image) implies a generation/write operation, it doesn't disclose important behavioral traits like whether this creates files on disk (implied by outputDir parameter), what permissions might be needed, whether it's idempotent, or what happens on failure. The description is minimal and lacks operational context.

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 a single, efficient Chinese sentence that directly states the tool's core function. It's perfectly front-loaded with zero wasted words or redundant information. Every character earns its place in conveying the essential 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?

For a 7-parameter tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what a 'knowledge card image' is, what the output looks like (file format, location, naming), or provide any context about the transformation process. Users must infer everything from parameter names and schema descriptions alone.

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 input schema already documents all 7 parameters thoroughly. The description adds no parameter semantics beyond what's in the schema - it doesn't explain relationships between parameters (like quality only applying to jpeg format) or provide usage examples. The baseline score of 3 reflects adequate but minimal value addition.

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: '将Markdown内容转换为知识卡片图片' (Convert Markdown content to knowledge card image). It specifies both the input (Markdown content) and output (knowledge card image), but doesn't differentiate from sibling tools like 'convert_markdown_to_card' which appears to have similar functionality.

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 no guidance on when to use this tool versus alternatives. There's no mention of sibling tools like 'convert_markdown_to_card' or 'list_available_themes', nor any context about when this specific image generation tool is preferred over other conversion options.

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