session.import

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

No annotations are provided, so the description carries the full behavioral burden, and it barely delivers. It implies a mutation ("into a profile") and some unsealing/decryption step, but says nothing about side effects, whether existing profile data is overwritten, permissions, or whether the operation is reversible.

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?

It is a single short sentence, so it is not verbose, but the phrase "such a bundle" is empty without context and makes the sentence fail to communicate. This is under-specification masquerading as conciseness, similar to the calibration example that scored 2.

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?

With no annotations and no output schema, the description must fully explain the operation, but it omits what a bundle is, where it comes from, what happens to the existing profile, and what a caller should expect. For an import tool that writes into a profile, this is materially incomplete.

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 input schema has zero parameters, and the rules set a baseline of 4 for that case. There is no parameter meaning the description could add, so this dimension is appropriately neutral.

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?

It gives a verb ("unseal") and a target ("a profile"), so the general import-into-profile action is inferable, especially next to the sibling session.export. But "such a bundle" is a dangling reference with no antecedent, and the description never states that this is a session bundle, leaving the resource only vaguely defined.

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 guidance on when to use this versus session.export, profile.update, or any other sibling. It does not mention prerequisites (e.g., needing a bundle produced by session.export) or when the tool should not be used.

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