import_har

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

No annotations are provided, so the description carries full burden. It states the tool imports data but doesn't disclose behavioral traits like whether this overwrites existing data, requires specific file formats beyond HAR/JSON, has rate limits, or what happens on success/failure. The 'as fallback' hint is vague and doesn't clarify the tool's role.

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, efficient sentence with no wasted words. It's appropriately sized for a simple tool and front-loads the core action ('Import a HAR file').

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 1 parameter with 0% schema coverage and an output schema exists, the description is minimally adequate. It covers the basic purpose but lacks details on usage context, behavioral implications, and parameter specifics. The output schema reduces the need to explain return values, but more guidance would help.

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 0%, so the description must compensate. It mentions 'HAR file (or line-delimited JSON entries)' which adds some context about the file_path parameter's expected content, but doesn't specify format details, constraints, or examples. This partially compensates but leaves significant gaps.

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 the tool imports a HAR file or line-delimited JSON entries, which is a clear verb+resource combination. However, it doesn't differentiate from sibling tools like 'analyze_api' or 'ingest_status' that might also handle data ingestion, and the 'as fallback' phrase is ambiguous without context.

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 provides no guidance on when to use this tool versus alternatives. It mentions 'as fallback' but doesn't explain what it's a fallback for or when other tools like 'ingest_status' or 'analyze_api' should be preferred. There are no explicit when/when-not instructions.

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