load_har

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

With no annotations, the description must disclose side effects. It states the tool saves the HAR as the 'default analysis dataset', but does not mention whether it overwrites existing data, validates the HAR format, or handles network authentication for URLs. This lack of behavioral detail is a significant gap for a mutating 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 one sentence, front-loaded with the action ('load HAR'), and contains no filler or redundant information. Every word earns its place.

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?

The tool is simple with a single fully-described parameter and an output schema. The description covers the core behavior, and the sibling list makes its role clear. However, it would benefit from a note about being a prerequisite for analysis tools, so it is not a 5.

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 provides 100% coverage for the 'source' parameter, including supported path types and the side effect of saving as default dataset. The tool description adds no additional semantic meaning beyond what the schema already documents, so it stays at the baseline.

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 HAR files from file path or HTTP URL and saves as default analysis dataset'. This is a specific verb+resource combination, and it distinguishes itself from the sibling analysis tools (list_urls_methods, get_request_details, etc.) which operate on already-loaded data.

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 context makes it obvious this is the ingestion tool used before analysis tools, since siblings are all query/analysis functions. However, it does not explicitly state 'use this first' or mention exclusions/alternatives, so it falls short of a 5.

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