flutter_build

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

No annotations are present, so the description carries the full behavioral burden. It does warn that the operation 'can take a long time', which is useful, but it fails to disclose what the tool returns, where artifacts are written, whether the build runs asynchronously, or how failures surface. Given the sibling flutter_get_result and flutter_logs, this missing context is significant.

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 two short sentences with no filler. The core action and target examples come first, followed by the practically important warning about long execution time. Every sentence earns its place.

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?

Despite full parameter coverage, the description omits important operational context for a long-running build tool: what happens after completion, how to retrieve results, whether it is synchronous, and what prerequisites or failure modes exist. The warning about duration is helpful but not enough for an agent to fully anticipate 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 description coverage is 100%, so the baseline is 3 even though the description adds no parameter-level detail. The description's platform examples overlap with the schema's target parameter, but it does not add new meaning or clarify edge cases beyond what the schema already documents.

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 uses a specific verb and resource: 'Build a Flutter app for a target platform', and gives concrete examples like apk, ios, and web. It is clearly distinct from run/test/analyze tools, but it does not explicitly differentiate itself from the similarly named sibling flutter_build_runner.

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 when to use the tool: when you want a build artifact for a target platform rather than running or testing the app. However, it gives no explicit guidance about when not to use it or which sibling should be chosen instead, such as flutter_run for execution or flutter_build_runner for code generation.

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