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, yet it discloses nothing. It does not mention that the tool generates files, that omitting 'apply' yields a dry run, that overwrite defaults to false, or that files are written relative to a project root — all behaviors an agent must know before invoking a scaffolding mutation.

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 short, but its brevity stems from under-specification rather than efficiency. It reads as a title fragment with a redundant parenthetical, so nothing is front-loaded because nothing substantive is said.

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 4-parameter mutation tool with no annotations and no output schema, meaning the description must explain what happens on invocation and what is produced. It says nothing about generated output, dry-run behavior, or file-writing semantics, leaving the definition wholly inadequate for correct invocation.

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 every parameter is already fully documented in the schema (apply/dry-run, outputDir default, overwrite default, projectRoot default). The description adds no parameter meaning, but the baseline of 3 applies when the schema does the heavy lifting.

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 essentially the tool name restated: 'MediaSFU React Native Expo :: app.scaffold (scaffold).' It conveys that this is a scaffolding tool for the React Native Expo SDK, but adds no verb+resource detail beyond the identifier itself, and offers nothing to distinguish it from the many sibling app.scaffold tools across other platforms.

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 guidance on when to use this tool versus alternatives such as integration.plan or room.bootstrap, nor any mention of prerequisites or when-not-to-use conditions. The description provides no usage context whatsoever.

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