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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds non-obvious behavior: telemetry and in-house automation crashes are excluded, groups are deduped by signature in count-desc order, and a group flagged unsymbolicated is keyed on image+offset rather than symbols. These are meaningful disclosures beyond the annotations, though permissions or pagination behavior are not addressed.

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?

Dense but well front-loaded: purpose, output shape, dedup semantics, then the routing hint. Every sentence carries information, though the parenthetical enumerations of aggregate dimensions make it slightly heavy for a single-parameter tool.

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?

With no output schema, the description compensates by explaining the return values (aggregate analytics and the groups structure with exampleIds) and the keyed-by-image+offset caveat. Nothing an agent needs to call this tool correctly appears to be missing.

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?

Only one parameter (udid) exists and schema coverage is 100%, so the schema already documents it as 'iOS device UDID'. The description adds no format or sourcing detail beyond that, which is the expected baseline when structured fields carry the full param burden.

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 (List) and resource (crash reports on an iOS device), then enumerates the exact output shape (total, per-app, per exception type, per-day timeline) and the `groups` structure. It clearly distinguishes itself from ios_crash_detail by naming the full-log alternative, so an agent can route without opening schemas.

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?

Explicitly routes the agent to ios_crash_detail with a returned crash id for full logs and notes that no automation session is required, which is a real prerequisite signal. It does not, however, distinguish itself from other crash siblings such as ios_crash_list or ios_crash_symbolicate, leaving some selection ambiguity.

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