last_crash

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

No annotations are provided, so the description fully covers behavioral aspects: it describes the data source (dumpsys dropbox), types of crashes (JVM/React-Native and native), and that it returns full exception headers and stacks. The only minor gap is not mentioning that the operation is read-only or any impact on system state, but it clearly implies a read 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 sentences, each earning its place: the first sentence states the tool's capability and source, the second provides usage guidance and rationale. It is front-loaded with the essential purpose.

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?

Given that there are only 2 parameters, no required parameters, no output schema, and no annotations, the description is adequately complete. It explains the tool's purpose, usage advice, and filtering option. The only missing aspect is specifying the return format, but without an output schema this is a minor gap.

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 baseline is 3. The description adds context for the 'package' parameter (how to filter) but does not add meaning beyond what the schema already provides. The 'serial' parameter is standard across sibling tools and requires no additional explanation.

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 states the tool returns the most recent app crash from the system DropBox, specifying the source (dumpsys dropbox) and type (JVM/React-Native and native crashes). It distinguishes itself from siblings like logcat by explaining it retrieves full exception headers and stacks in one call.

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 explicitly states when to use this tool: 'Use this instead of grepping logcat when an app just crashed', and gives a clear alternative (logcat). It also explains the advantage (DropBox keeps the whole fatal, even after it has scrolled out of logcat).

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