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

The description contradicts the annotation idempotentHint=false by stating 'Duplicates of memories oriiion already holds are skipped, so calling this twice is safe,' which effectively claims idempotent behavior. Because the description contradicts a structured annotation, this is an annotation contradiction and scores 1 regardless of other useful context provided.

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 long but front-loads the purpose and then provides necessary procedural detail. Every sentence adds information about preconditions, formatting, or duplicate handling, though the density and length keep it from being maximally concise.

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 two-parameter write tool with no output schema and existing annotations, the description covers purpose, preconditions, format, and duplicate behavior. It is nearly complete, though it could mention return values or failure modes, and the idempotency contradiction slightly undermines correctness.

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 100%, so baseline is 3. The description adds meaningful detail beyond the schema: it specifies the exact category headers (Instructions, Identity, Career, Projects, Preferences), requires verbatim user wording, and clarifies date formatting. This extra semantic guidance justifies a 4.

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?

States a specific verb and resource: storing another AI assistant's memories into oriiion. It names the outcome (oriiion's assistant knows the user from the first message) and distinguishes the operation from all sibling tools, none of which handle cross-assistant memory import.

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 says the caller must PRODUCE the export themselves and that there is no API to read another provider's memories. It gives clear preconditions and formatting requirements. It does not name alternative tools or explicit when-not-to-use cases, 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.