crashes_search

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 only discloses the default and maximum limit and pagination metadata; it omits any side effects, permissions, rate limits, or what the search actually does with the filters. This is minimal for a complex search tool.

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 short and front-loads the most operationally important note (limit/pagination). However, it is under-specified for a tool with 14 parameters; the brevity comes at the cost of essential context, making it less effective than a more balanced length.

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?

Despite having an output schema, the description does not explain how to structure searches, interpret pagination metadata, or which filters are mutually exclusive. The tool is complex and lacks annotations, so the description should provide more contextual guidance; it does not.

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 schema has 0% description coverage across 14 parameters. The description adds meaning only for 'limit' (default 25, max 200), but none of the other 13 filter parameters (e.g., app_id, os_versions, created_after) are explained. This is a significant gap.

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 'Search crash submissions with advanced filtering'—a specific verb, resource, and scope. The phrase 'advanced filtering' hints at differentiation from simpler sibling list tools, although it does not name them explicitly.

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 only usage guidance is about pagination limits and defaults ('Default limit is 25... Max 200. Use pagination metadata for additional pages'), but it does not explain when to use this tool over crashes_list or crashes_get_by_id, nor any exclusions or alternatives.

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