generate_flutter_mock_factory

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

With no annotations, the description carries the transparency burden. It does disclose meaningful behavior: generated artifacts are realistic but fake, and repositories are in-memory, implying no persistence. However, it does not say whether the tool writes files, modifies an existing Flutter project, or introduces dependencies, so the side-effect profile is only partially disclosed.

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 one efficient sentence with no filler. It front-loads the action and artifact types and then adds the use-case context, earning its length.

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 generator with no output schema and no annotations, an agent needs to know what fields maps to, what itemCount controls, and what happens to the project after generation. The description only hints at the overall purpose, leaving important operational details unexplained.

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 only 33%: domainName is documented, but fields and itemCount are not. The description does not mention either parameter, so it fails to compensate for the schema gap. The word 'domain' weakly relates to domainName, but the semantics of fields and itemCount are left to inference.

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 names a specific verb ('Generates') and concrete resources ('mock data factories', 'fake entities', 'in-memory mock repositories'), and connects them to a clear use case ('hackathon UI prototyping'). This makes it easy to distinguish from sibling generation tools like golden tests, API bridges, or chart generation.

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 phrase 'for instant hackathon UI prototyping' gives clear context for when this tool is appropriate. It does not explicitly name alternatives or state when not to use it, but the mock-specific wording strongly implies the intended scenario.

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