generate_flutter_platform_config

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 behavioral disclosure. It mentions what files are generated but does not state whether it overwrites existing files, whether it requires an existing Flutter project, whether it is idempotent, or what the return value is. For a tool that likely writes multiple files, this is a significant gap in transparency.

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, well-structured sentence that front-loads the core action, lists specific outputs, and wastes no words. It is appropriately sized for the tool's purpose and easy to parse at a glance.

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 three parameters, one required, with enums and defaults, and no output schema, the description is inadequate. It does not clarify the output format, whether it modifies existing project files, what the 'Web WASM CanvasKit bootstrap' entails, or any side effects. An agent would be uncertain about the tool's behavior after reading this, making it incomplete for effective invocation.

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% (only projectName has a description). The description adds no extra meaning to permissions or targetPlatforms beyond the schema enums and defaults. It does not explain the format or purpose of these parameters. Since the coverage is low, the description should compensate but does not, leaving the agent to infer semantics from names and enums alone.

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 a specific action ('Generates'), the resource ('native platform configurations'), and enumerates concrete outputs (iOS Info.plist permission strings, AndroidManifest.xml permissions, Web WASM CanvasKit bootstrap). This clearly distinguishes it from sibling tools like audit_flutter_codebase or generate_flutter_cicd_pipeline. An agent can immediately understand its purpose without inspecting the schema.

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 does not explicitly state when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites. However, the specificity of 'generates native platform configurations' strongly implies the appropriate use case, and the sibling tool names do not overlap with this functionality. There is no misleading guidance, but the lack of explicit alternatives or when-not-to-use leaves room for improvement.

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