ios_doctor

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

No annotations are present, so the description carries the full burden. It discloses that the audit works without Xcode and that results are returned as issues sorted by severity with fixes, which is useful. However, it does not explicitly state that the tool is read-only and does not modify the project, and it is silent on whether any network access, authentication, or environment prerequisites are needed.

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 dense and front-loaded with the core action and constraint, then packs a precise list of audit areas into one sentence. It avoids filler and each phrase adds specificity, though the long single-sentence list could be slightly easier to scan if split into short bullet-like clauses.

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?

There is no output schema, but the description does communicate the return shape: issues sorted by severity with fixes. It also names all major audit domains, making the tool's scope clear. It could be more complete about return format and side effects, but for a diagnostic tool with one optional parameter, the essential context is present.

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 0%, so the description should compensate, but it never mentions project_path, its meaning, default behavior, or how it relates to the project root. The schema only provides a title and nullable default, which is thin. For a single self-explanatory parameter this is a moderate gap, but still below the bar set for low-coverage schemas.

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 uses a specific verb ('Audit') with a clear resource ('ios/ side of a Flutter project without Xcode') and enumerates concrete check items (bundle id, Info.plist usage strings, deployment target, icons, launch screen, privacy manifest, Firebase config, entitlements). This clearly distinguishes it from sibling tools like ios_set_info_plist_value or ios_get_build_settings, which are mutation/retrieval tools rather than a holistic audit.

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 usage as a diagnostic audit step before iOS build/release actions, but it never explicitly states when to prefer this over mac_doctor or the individual ios_get_* inspection tools. There are no exclusions or alternative routing, so the agent must infer the appropriate context from the audit-oriented wording.

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