mcp__getFlutterGenerator

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

No annotations are provided, so the description bears full responsibility. It discloses that the tool downloads images, rewrites references, and generates manifests, implying file system modifications. However, it does not state if these actions are reversible, require permissions, or have side effects like overwriting existing files.

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 paragraph that front-loads the activation instruction and then lists functionalities. It is reasonably concise with no redundancy, though it could be improved by using bullet points for readability.

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 has 5 parameters, no output schema, and moderate complexity, the description covers the workflow but lacks details on expected return values, error handling, or what happens when parameters are invalid. It is adequate but not fully comprehensive.

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 each parameter already has a description. The tool description adds no additional semantic detail beyond what's in the schema, except reinforcing the requirement for rootPath. Per guidelines, baseline is 3.

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 gets the Flutter component development workflow. It lists specific deliverables (DSL mapping, asset download, etc.), establishing a distinct purpose. However, it does not explicitly differentiate from sibling tools like mcp__getComponentGenerator, which could be confused. The purpose is clear but lacks sibling distinction.

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 explicitly states when to call the tool: 'When Flutter Generator or Flutter Component is mentioned, please actively call this tool.' It also notes the requirement for an absolute rootPath. However, it does not provide alternative tools or when not to use it.

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