suggest_settings

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

Describes read-only behavior, no side effects, returns ranked list or 'no history' message. No contradictions with missing annotations; description carries full burden adequately.

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?

Five sentences covering purpose, usage, behavior, and limitations. Front-loaded with primary function. No redundant phrases.

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?

Explains return format, database source, and relationship to sibling tool. No output schema but description sufficiently covers expected output. Adequate for agent decision-making.

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 coverage is 100%, so baseline is 3. Description adds context about narrowing results and default behavior (returns top settings across all history), but does not significantly extend schema descriptions.

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?

Clearly states action ('Recommend concrete, proven settings') and resource ('local generation-history database'). Distinguishes from sibling tool generation_stats by specifying different use cases.

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?

Explicitly states when to use ('ready-to-apply values') and when to use alternative (generation_stats for aggregate counts). Mentions read-only and independence from ComfyUI.

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