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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the genuinely useful fact that the payload is portable and can be recreated outside the current host, including on self-hosted verdigraph-neurogenesis. It does not say what the state document contains or whether any ownership/auth constraints apply.

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 short and the key concept (portable state document) is front-loaded, but as a sentence fragment it omits the action verb and leaves the parenthetical to carry important round-trip semantics. Brevity here comes at the cost of specification rather than being earned.

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?

An output schema exists, so the return shape need not be explained. Still, for a tool whose whole purpose is producing a migratable artifact, the description omits what is captured in the state, whether secrets are included, and any preconditions — gaps an agent would want closed before exporting.

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% for the single required agent_id parameter, and the description never mentions it. The agent must infer from the name alone whether this is the target agent, the exporting caller, or something else — the description does not compensate for the schema gap.

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 names the artifact produced (a 'portable state document for an agent') and pairs it with its inverse, import_state, which helps separate it from that sibling. But it never uses a verb form ('export'), and it gives no signal to distinguish this from describe_agent or get_agent, which also surface agent information.

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 when-to-use guidance — nothing says when an agent should export state versus calling get_agent or describe_agent. The only contextual cue is the implicit round-trip with import_state, which the agent must infer from the parenthetical.

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