env.preflight

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

With no annotations, the description must carry the full behavioral burden. It only says 'check', implying a read-only operation, but does not disclose whether it modifies anything, what it returns, or any side effects. It also omits operational details like network access or installed tooling requirements. This is a significant gap for a tool that likely performs environment inspection.

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 a single, concise sentence that is front-loaded with the primary verb and object. It wastes no words and is easily parsed. However, it is so brief that it omits crucial detail, which is a structure vs. completeness trade-off, but for conciseness alone it earns a 4.

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?

Given the tool's simplicity (one optional parameter, no output schema, no annotations), the description still lacks essential information: what 'readiness' actually checks (e.g., SDK versions, environment variables), the format of the result, and the acceptable values for 'target'. An agent would struggle to use this tool correctly without additional context.

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?

The schema has one optional parameter 'target' with zero description (0% coverage). The description hints that 'target' selects an environment (Android, iOS, etc.) but does not specify valid values, the default behavior when omitted, or whether it accepts comma-separated lists. The agent cannot reliably construct the correct input without guessing.

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 clearly states the tool's purpose: checking host/project readiness across specific environments (Android, iOS, Flutter, React Native, CI) or all. This is a specific verb-resource pair and distinguishes it from siblings like env.ensure_appium (which ensures Appium) and env.compatibility_matrix (which builds a matrix).

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?

The description implies the tool is used to assess readiness before proceeding, but it does not explicitly state when to use it instead of alternatives, nor does it mention any exclusions or prerequisites. The environment list gives context, but there is no direct guidance on selection criteria compared to related tools.

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