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 bears full burden. It describes the tool as parsing and returning data, implying non-destructive behavior. However, it lacks explicit disclosure of behavioral traits such as read-only nature, performance characteristics, or any side effects, which would be helpful for an agent.

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 long, front-loads the key action and schema, and contains no redundant information. Every sentence adds value.

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 5 parameters, full schema coverage, and no output schema, the description adequately conveys the overall purpose and return shape. It could be enhanced by briefly noting the response format options (e.g., JSON/markdown) but is largely complete for typical use.

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 the base is 3. The description adds overall behavioral context (what the tool returns) but does not add specific parameter semantics beyond what is already in the schema. The summary of return values is useful but not parameter-level detail.

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 that it parses the `animation-hitches` schema from a `.trace` bundle, enumerates the outputs (hitch totals, by-type counts, longest hitches, 100ms threshold crossing), and implicitly distinguishes itself from siblings like `analyzeHangs` or `analyzeTimeProfile` by its specific domain.

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 implies usage for animation hitch analysis from a specific `.trace` bundle recorded with the Animation Hitches template, providing clear context. However, it doesn't explicitly exclude other scenarios or compare directly with sibling tools, leaving some ambiguity about when to prefer this over others.

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