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 discloses that 'Artifacts are stored, never executed', which is a key safety behavior. However, it does not mention idempotency handling, error behavior, or write implications beyond storage. The description adds some value but lacks depth.

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, compact and to the point. It front-loads the core purpose and includes a key behavioral constraint. No fluff or redundancy.

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 tool with a required nested object, three required parameters, no output schema, and no annotations, the description is insufficient. It does not explain what the history object contains, what idempotencyKey means, or what happens after import. Agents cannot fully understand how to construct valid calls or interpret results.

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 does not explain any of the three parameters (id, history, idempotencyKey) or the nested structure of history. The schema provides field names, but their meanings and relationships are not clarified. The description adds no parameter-level information.

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 verb 'Import' and the resource 'research history', and specifies 'fixed externally produced results with original attribution'. This gives a clear purpose, though it does not explicitly differentiate from sibling tools like record_history or create_research_run.

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?

There is no explicit guidance on when to use this tool versus alternatives. The phrase 'fixed externally produced results' implies a specific context, but it doesn't name any sibling tools or provide conditions for selection. No when-not-to-use guidance is given.

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