Analyze animation hitches from a .trace bundle

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 states 'Parse' implying a read-only analysis, and lists the computed results. It does not mention side effects or permissions, but the nature of the tool (analyzing a trace file) strongly suggests no destructive 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?

The description is a single, dense sentence that front-loads the essential information. Every element (schema, template, return types) is included without redundancy or filler.

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 the lack of an output schema, the description adequately summarizes the return values. It could be more precise about the data structure (e.g., whether it's a list or object), but given the simplicity of the tool and the presence of clarifying sibling names, it is sufficiently 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 input schema already has 100% coverage with detailed descriptions for all three parameters. The description adds contextual value by noting the Apple 100ms threshold, which aligns with the minDurationMs parameter. This goes beyond the schema's baseline for a high-coverage case.

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 parses animation-hitches data from a .trace bundle recorded with a specific template, and it lists the exact outputs (totals, by-type counts, longest hitches, 100ms threshold). This distinguishes it from sibling tools like analyzeHangs or analyzeTimeProfile.

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?

While the description specifies that the trace must be recorded with the Animation Hitches template, it does not explicitly contrast with alternatives or advise when not to use it. However, the context is clear enough for an agent to infer appropriate usage.

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