FluxMCP

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

No annotations provided, so description carries full burden. Explains the async polling pattern and relationship to generation tasks well. However, lacks explicit safety disclosure (read-only nature) or error scenarios (e.g., invalid task_id handling) that would be necessary for a full behavioral profile.

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?

Well-structured with clear sections: purpose declaration, usage explanation, conditional bullet points, and return value summary. Front-loaded with key action. Minor redundancy between first and second sentences, but overall efficient given the complexity of the async workflow being explained.

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 output schema exists (per context signals), the brief return description is acceptable. Covers the essential async workflow pattern and task lifecycle. Could mention error states or batch retrieval alternative (flux_get_tasks_batch), but sufficient for agent invocation decisions.

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%, establishing baseline 3. The description contextualizes task_id usage in the bullet points ('initial generation returned a task_id'), but does not add syntax, format constraints, or examples 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?

Opens with specific verb 'Query' and clear resource 'Flux image generation task', specifying scope (status and result). Effectively distinguishes from sibling generation tools by positioning this as the retrieval/polling mechanism versus the creation mechanism.

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?

Explicit 'Use this when:' section with four specific scenarios that clearly differentiate this from flux_generate_image and flux_edit_image, explicitly mentioning the async callback pattern and task_id workflow. Provides clear guidance on when to prefer this over immediate-return paths.

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