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 mention that the default is a dry-run and that files are only written when apply=true, nor that outputDir/overwrite interact with existing content — all of which is exactly the kind of behavior an agent needs before running a file-generating tool.

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 with the namespace, so there is no wasted prose. However, the only content is a name restatement and an alias list, which means the brevity comes from under-specification rather than tight writing.

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?

With no annotations, no output schema, and four parameters for a tool that writes to the filesystem, the description is materially incomplete: it omits the dry-run-by-default semantics and any note on what the scaffold produces. The schema alone lets an agent invoke the tool, but not understand the consequences.

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 every parameter (apply, outputDir, overwrite, projectRoot) is documented in the schema with defaults and constraints, so the baseline of 3 applies. The description adds nothing beyond the schema and does not explain how the parameters interact.

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 text is essentially the tool name restated ('app.scaffold (scaffold)') plus a platform/alias tag list; it never states what scaffolding actually produces or which files/directories it generates. The 'swift::' prefix and aliases (apple, ios, macos, swiftui) do help route to the Apple-platform sibling rather than android/flutter/etc., but that is naming, not purpose.

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 at all: nothing tells the agent whether scaffold should run before env.preflight or feature.map, or how it relates to integration.plan or room.bootstrap. The alias list implies 'use this for Swift/Apple projects' but that is inference, not stated guidance.

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