generation_stats

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

With no annotations provided, the description fully carries the burden. It explicitly states 'Read-only' and clarifies that it works without ComfyUI. It also discloses that stats are from local database and returns empty until generations exist, leaving no ambiguity about 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 concise and well-structured: first sentence states purpose and details, second adds behavioral info, third provides usage guidance. No unnecessary words, every sentence adds value.

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 simplicity (one optional param, no output schema), the description is complete. It explains what stats are returned, when they are available, and that the source is local database. No gaps.

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?

The schema already describes the optional model_family parameter. The description adds examples ('e.g. sdxl, flux, qwen_image, illustrious'), which enriches understanding. Schema coverage is 100%, so baseline is 3; description provides extra context, justifying a 4.

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 'Show statistics from this MCP server's local generation-history database' and lists specific stats. It distinguishes from sibling suggest_settings by explicitly saying 'For concrete recommended settings rather than aggregate counts, use suggest_settings.'

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 when-to-use guidance: 'Read-only; works without a running ComfyUI' and notes that it returns empty until generations exist. It also directs to suggest_settings for concrete recommendations, helping choose between tools.

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