design_flutter_ui

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

No annotations are provided, so the description carries the full burden of behavior disclosure. It states what the tool produces (widgets, layouts, state integration, animations) but not HOW results are delivered — whether it writes files, returns code, or generates a design spec. The design-oriented phrasing makes its non-destructive nature inferable, but the output mechanism remains unspecified, which matters for a code-generation tool.

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?

A single, well-constructed sentence with zero filler. The most distinctive content (Material 3 responsiveness, state management options, animations) is front-loaded, giving an agent immediate signal about what this tool does without wading through prose.

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 tool with four well-documented parameters and no output schema, the description covers the what but not the full how — notably the output delivery format and any workflow expectations (e.g., does it expect a prior decompose_flutter_prompt call?). It's adequate but leaves the agent guessing about invocation results, which a richer description could resolve.

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%, so the baseline of 3 applies. The description adds modest value beyond the schema by hinting at the design philosophy (Material 3, responsive, production-ready) that shapes output, but it doesn't detail parameter usage or format expectations beyond what the schema already documents.

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 uses a specific verb ('Designs') with a clear resource (Flutter UI) and enumerates concrete deliverables: widgets, Material 3 responsive layouts, Riverpod/Bloc state integration, and animations. This distinguishes it cleanly from siblings like scaffold_flutter_backend or generate_flutter_platform_config, which target entirely different concerns.

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 for UI-design work through its focus on widgets, layouts, and state management, but it doesn't explicitly state when to use it versus alternatives or mention exclusions. No sibling is named, and the boundary against tools like decompose_flutter_prompt (prompt decomposition) or generate_flutter_charts (a narrow UI subset) is left to inference.

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