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

With no annotations, the description carries the full behavioral burden and delivers none of it. It never discloses the dry-run default (which the schema's 'execute' parameter reveals), whether the command mutates the project, what permissions or credentials it needs, or what the check reports. An agent cannot infer the blast radius of this tool from 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?

The single fragment is short but not concise in the useful sense - it is under-specified rather than efficient, consuming a line without conveying any actionable information. Nothing is front-loaded because there is nothing to front-load.

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 zero-required-parameter tool with no annotations and no output schema depends entirely on the description to explain what it checks and what the result means, and the description supplies none of that. An agent has no basis to decide whether to invoke it or how to interpret its result.

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 both parameters are documented in the schema, including the important 'omitted means dry-run' semantics for execute. The description adds no parameter meaning beyond that, 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 a restatement of the tool name and namespace ('MediaSFU React Native :: env.preflight (command)') rather than a statement of what the tool does. It never says what a 'preflight' inspects or returns, and it does nothing to distinguish itself from the parallel android::/flutter::/swift::env.preflight siblings. This is tautology, 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: no mention of when a preflight should be run, what prerequisite state it assumes, or how it relates to siblings like runtime.diagnose, sdk.recommend, or app.scaffold. The parenthetical '(command)' is the only hint that it performs an action.

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