raw_crash_report

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

Description discloses that it may open a dialog or change project state, which is important since no annotations are provided. It also advises inspecting the command name first, adding a layer of caution, though it remains somewhat vague about exact side effects.

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?

Description is concise, comprising two sentences that convey purpose, argument expectations, and side-effect warnings without unnecessary verbosity.

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 tool with no parameters and no output schema, the description covers purpose, usage, and side effects adequately. It could be improved by elaborating on what the report contains or how it is delivered, but it is otherwise 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?

The tool has no parameters, so the description adds clarity by confirming it is 'no-argument'. Since schema coverage is complete (no properties), the baseline of 4 is appropriate and the description reinforces the lack of arguments.

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 it generates a support report for troubleshooting, which is a specific verb and resource. It distinguishes from sibling raw_* commands by its unique purpose of crash report generation.

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?

Provides usage guidance by noting it is a static no-argument action and warns about potential side effects. However, it does not explicitly contrast with alternative tools or specify when to prefer it over other commands.

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