flutter_build

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. 'Build' implies a potentially long-running, resource-intensive process that generates output files, but the description doesn't mention execution time, side effects (e.g., creating build artifacts), error handling, or output location. It lacks critical context for safe and effective use.

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, efficient sentence that front-loads the core purpose without unnecessary words. Every word earns its place, making it easy to parse quickly. No structural issues or redundancy are present.

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 complexity of a build tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., success status, build artifacts, error messages), behavioral traits like timeouts or file system changes, or how it differs from siblings like flutter_release_build. This leaves significant gaps for agent understanding.

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%, with clear documentation for all parameters (cwd, target, buildMode, flavor). The description adds no additional parameter semantics beyond implying that 'target platform' relates to the 'target' parameter. Since the schema does the heavy lifting, the baseline score of 3 is appropriate.

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 verb ('Build') and resource ('Flutter app') with the specific scope 'for specific target platform'. It distinguishes from siblings like flutter_clean, flutter_run, and flutter_test by focusing on compilation rather than cleaning, execution, or testing. However, it doesn't explicitly differentiate from flutter_release_build, which appears to be a specialized sibling.

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 provides no guidance on when to use this tool versus alternatives like flutter_release_build or flutter_run. It doesn't mention prerequisites (e.g., Flutter project setup), exclusions, or contextual triggers. The agent must infer usage from the tool name and parameters alone.

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