Get Crash Report

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

Annotations already mark as read-only (readOnlyHint: true). Description adds that it returns the 'full content', but no additional behavioral traits beyond what annotations provide.

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?

Two tightly written sentences that efficiently convey purpose and usage hint. No extraneous words; front-loaded with key action.

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-described parameters and read-only annotation, the description is sufficient. Lacks output format details, but 'full content' implies sufficient context.

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 already describes both parameters (device and id) with descriptions. Description only reiterates that retrieval is by ID, adding no new meaning.

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?

Description clearly states the tool retrieves the full content of a crash report by ID. Includes reference to sibling mobile_list_crashes for finding IDs, distinguishing it from other tools.

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 instructs to use mobile_list_crashes to find available IDs, providing a clear prerequisite. Does not explicitly state when not to use, but context implies sequential usage.

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