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

No annotations are provided, so the description carries the full burden. It discloses the output (metadata + raw content) and the lack of session requirement, which is useful. However, it does not state whether the operation is read-only, has side effects, or requires any special permissions. For a retrieval tool, these are relevant but not critical omissions, leading to a moderate score.

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, front-loaded sentence that communicates the tool's primary function and key constraint without any fluff. Every word contributes value: 'Full parsed metadata + raw content' defines output, 'one crash report' specifies scope, 'by id from ios_crash_analytics' explains the input, and 'No automation session required' provides a usage condition. It is an exemplar of concise, structured description.

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 retrieval tool with two well-documented parameters and no output schema, the description adequately informs an agent: what it returns, how to identify the report, and that no session is needed. It does not mention error handling or the exact structure of the returned metadata, but that is often unnecessary. The description covers the essential operational details, making it nearly complete for its simplicity.

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%, with both parameters (id and udid) already described clearly. The description adds the context that the id comes from ios_crash_analytics, which reinforces the schema's 'Crash report id (file name) from ios_crash_analytics' but adds no new syntactic or semantic detail. With high schema coverage, the baseline of 3 is appropriate.

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 retrieves 'Full parsed metadata + raw content of one crash report' and specifies the source of the id ('by id from ios_crash_analytics'). It distinguishes itself from sibling tools like ios_crash_analytics (which likely lists/analyzes) and ios_crash_list by focusing on a single report's details. The verb is implicit but unambiguous, and the resource and scope are precise.

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 a prerequisite (obtain id from ios_crash_analytics) and states a condition ('No automation session required'). However, it does not explicitly state when to use this tool over alternatives like ios_crash_list or ios_crash_symbolicate, nor does it mention exclusions or alternative scenarios. The guidance is implied rather than explicit.

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