generate_flutter_component_from_figma

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

The annotation readOnlyHint=true already informs the agent this is a safe read operation. The description adds context about 'minimal' output and 'federated docs mapping', but does not clarify what that mapping entails or any limitations. It does not contradict annotations.

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, front-loaded sentence with no waste. However, it is efficient at the cost of omitting important details, so it earns a 4 rather than 5.

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?

With 5 parameters, no output schema, and no parameter descriptions, the description is too minimal. It fails to explain the output format, the behavior of optional parameters, or the 'federated docs mapping' concept, leaving significant gaps for an agent to safely invoke the tool.

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?

The schema has 0% parameter description coverage, so the description must compensate. It only indirectly refers to figmaUrl via 'Figma node' but leaves depth, version, responseMode, and debugTelemetry completely unexplained, leaving agents without meaning for these parameters.

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's verb ('Generate'), resource ('Flutter widget snippet'), source ('Figma node'), and method ('federated docs mapping'). It distinguishes itself from sibling tools like generate_flutter_page_from_figma by targeting components vs pages.

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 the tool is for generating small widget snippets from Figma nodes, but it does not explicitly state when to use this instead of other tools such as get_figma_nodes or generate_flutter_page_from_figma. No prerequisites or exclusions are mentioned.

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