load_trace

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

Given no annotations, the description covers key behavioral aspects: loading, replacement, caching, error scenarios, and download failure. It does not explicitly state it's read-only or mention thread safety, but is still comprehensive.

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 well-structured with clear sections, but slightly lengthy. Each sentence adds value; front-loaded with purpose. Minor redundancy could be trimmed.

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 simple one-parameter load tool with no output schema, the description is complete: covers purpose, usage, behavior, errors, caching, and parameter specifics. Agent can use it correctly.

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?

Only one parameter (path) with full schema coverage. Description adds extra context: absolute path requirement, accepted formats, content-sniffing, and replacement behavior, augmenting the schema.

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 loads a Perfetto trace file for analysis, and positions it as the foundational tool that other tools rely on. This distinguishes it from siblings which operate on the loaded trace.

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?

Explicitly states when to use (starting any analysis session, call first) and when not to use (live capture, streaming URLs). Also provides error conditions and caching behavior.

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