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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing. It does not say that a dry-run happens by default (unless apply=true), that files may be written to disk, that existing files are only replaced when overwrite=true, or that projectRoot defaults to the MCP working directory – all critical for a file-generating operation.

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?

It is short, but the brevity is under-specification rather than conciseness – the single sentence carries no information beyond the identifier, so no sentence earns its place as useful content.

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?

For a 4-parameter file-scaffolding tool with no annotations and no output schema, the description explains nothing about what gets generated, where, or with what side effects. An agent cannot safely invoke this tool from the description alone.

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%, and the parameter descriptions are genuinely informative (apply=dry-run toggle, overwrite default false, projectRoot default, outputDir default path). The description adds nothing on top, so the baseline of 3 applies.

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 is 'MediaSFU Flutter :: app.scaffold (scaffold).' – a restatement of the tool name with a namespace prefix. It names neither a verb nor the resource being produced, and gives no way to distinguish it from the ~8 other platform-specific app.scaffold siblings.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as integration.plan or env.preflight. The agent must infer the scaffolding intent entirely from the tool name.

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