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: not that files may be written, not the dry-run default, not overwrite semantics, permissions, or reversibility. For an operation that mutates a consumer project, this is a serious gap.

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 text is short but that is under-specification rather than conciseness. It is a single redundant phrase that front-loads nothing useful and earns no place in the definition.

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?

A four-parameter, file-generating tool with no annotations and no output schema requires meaningful guidance, yet the description supplies none. Nothing tells the agent how to invoke it safely or what it produces.

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 all four parameters (apply, outputDir, overwrite, projectRoot) are already well documented in the schema. The description adds no parameter meaning beyond that, which is the baseline 3 case 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 merely restates the tool name and title: 'MediaSFU React Native :: app.scaffold (scaffold).' It never states what scaffolding actually accomplishes (e.g., generating SDK boilerplate files into a project). This is a tautology rather than a description.

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 indication of when to use this tool, what prerequisites exist, or how it differs from siblings like shared::app.scaffold or react-native-expo::app.scaffold. An agent has no basis for selecting this over the other platform scaffold tools.

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