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

No annotations are provided, so the description carries full behavioral burden, yet it discloses nothing about writes, dry-run, overwrite semantics, permissions, or side effects. Critical facts (that this generates files by default in dry-run mode) live only in the schema, not the description.

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 and front-loaded, but this is under-specification rather than conciseness. The single header-style line wastes space on aliases while omitting the one useful sentence about what the tool produces.

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?

This is a file-generating mutation tool with no annotations and no output schema, so the description must do the heavy lifting. Instead it provides nothing about behavior, defaults, or prerequisites, leaving the agent unable to call it safely or know when to use it.

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 coverage is 100%, so all four parameters (apply, outputDir, overwrite, projectRoot) are fully documented in the schema with defaults and constraints. The description adds no parameter meaning, so the baseline 3 for high-coverage schemas 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 only restates the tool name ('app.scaffold (scaffold)') plus a media/SDK qualifier and aliases. It never says what scaffolding does, what it generates, or for whom. It borders on a tautology of the title, with no verb+resource articulation.

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?

No when-to-use, when-not-to-use, or alternative guidance is given. With ~14 sibling tools per SDK (env.preflight, integration.plan, etc.), the agent gets no signal about when app.scaffold is the right choice. Only the alias list hints at scope.

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