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

No annotations are supplied, so the description carries the full behavioral burden and delivers nothing. It does not state whether the command mutates the project, what it checks, whether it requires credentials or network access, or what side effects 'execute' triggers versus dry-run.

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 a useful sense — it is under-specified rather than front-loaded with intent. There is no wasted wording because there is almost no wording at all.

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?

For a command that can actually execute a 'trusted manifest command' (per the schema's execute flag), with no annotations and no output schema, the definition omits all context an agent needs to call it safely or correctly.

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 ('execute' and 'projectRoot') are fully documented in the schema, including the dry-run default. The description adds no 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 restates the tool name and title ('mediasfu-shared :: env.preflight (command)') without explaining what a preflight command actually does. It identifies the namespace and that it is a command, which is marginally more than a pure name echo, but an agent gains no understanding of the operation's 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?

No guidance on when to run preflight, when to skip it, or which sibling (e.g. runtime.diagnose, runtime.readiness.diagnose, app.scaffold) to prefer is provided. The agent must infer usage entirely from the name.

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