mcp__getComponentGenerator

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

No annotations are provided, so the description must fully convey behavioral traits. It mentions saving files but does not disclose what exactly is created, whether it is destructive, or any side effects. The description is vague about the workflow structure.

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 short, consisting of three sentences. The first sentence is somewhat redundant ('Users need to actively call this tool'), but overall it is efficient.

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?

The description lacks details about the output (no output schema exists), such as the structure of the workflow or file types. With four parameters and no output specification, the description is incomplete for an agent to fully understand the tool's behavior.

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 each parameter already has a description in the input schema. The description only adds 'save workflow files' context for rootPath but does not significantly enhance understanding beyond the schema.

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 states it provides a component development workflow and requires a rootPath to save files. The verb 'get' is used, making the purpose clear. However, it does not differentiate from sibling tools like getFlutterGenerator or getD2c, which are likely different generators.

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 says 'When Generator is mentioned, please actively call this tool,' giving a clear when-to-use hint. It also emphasizes providing an absolute rootPath. However, no exclusions or alternative tools are mentioned, so guidance is limited.

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