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

With no annotations provided, the description carries the behavioral burden, and it does disclose one meaningful trait: no automation session is required. That said, it does not mention output format, whether a connected device is required beyond the udid parameter, or any side-effect implications, though 'list' implies a read-only operation.

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 two short sentences with no filler. The primary action is stated first, and the important 'no automation session required' note is appended efficiently without repeating schema information.

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 simple two-parameter list operation, the description plus schema is largely sufficient for correct invocation. The absence of an output schema is not critical here because 'List' implies a collection result, and the no-session requirement is clearly stated, though a note about the returned crash report file types would have made it complete.

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%, so the parameters 'udid' and 'pattern' are already documented in the schema. The description adds no additional detail about their semantics or formatting, so it does not go beyond the structured information.

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 ('List') and resource ('crash reports on an iOS device'), making the tool's purpose immediately clear. It is distinguishable from ios_crash_detail and ios_crash_analytics by the 'list' framing, though it does not explicitly name those alternatives.

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 phrase 'No automation session required' gives a useful prerequisite condition, telling the agent this tool can be used without setting up a session. However, it provides no guidance about when to prefer this over related crash tools such as ios_crash_analytics, ios_crash_detail, or ios_crash_symbolicate.

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