iOS Simulator: List Crash Logs

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

Annotations only cover readOnlyHint, so the description carries real behavioral weight: it explains where reports physically live (~/Library/Logs/DiagnosticReports), that output is filtered to simulators only and labeled by simulator, and that no boot is required. It also flags the non-obvious defaulting difference (device does not default to booted) — genuinely useful context beyond the annotations.

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?

Front-loaded with the core action, then layered with the most decision-relevant facts in a compact sequence. Every sentence earns its place; no filler or restatement of the name.

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 read-only list tool with no output schema, the definition supplies the location of the data, the filtering semantics, the follow-up tool, and the boot precondition — everything an agent needs to call it correctly and interpret the results.

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 coverage is 100%, so the schema already documents all four parameters, and the description mainly echoes `process`. However it adds interpretive value the schema lacks — that most results are system daemons, so `process` is the practical filter for finding your own app's crash.

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?

States a specific verb and resource ('List crash reports from simulator processes'), immediately scoping to simulators and ordering 'newest first'. It clearly distinguishes itself from the sibling ios_simulator_get_crash_log, which it names for reading individual reports.

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?

Gives concrete selection guidance ('pass `process` to find your app's') and routes the agent to the right sibling for the follow-up action. It also states an important precondition contrast ('Nothing needs to be booted'), though it does not explicitly exclude versus sibling listers like ios_simulator_read_logs.

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