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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds useful behavioral context: `format=json` returns the bundle object directly, and the result is portable/restorable via the import tool. This goes beyond the annotations without contradicting them.

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?

Two tight sentences with no filler. The core purpose and the most important usage detail (JSON round-trip with the import sibling) are front-loaded and immediately actionable.

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 low-complexity read-only export tool with strong annotations, the description is nearly complete. It explains what the tool does, how the JSON format behaves, and how to use the output. The only notable gap is the lack of detail on the zip format's behavior, but this is minor for agent invocation.

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 coverage is only 50%, and `agentIdOrAddress` has no schema description. The endpoint in the description implies it is the Agent's ID or address, but this is not explicitly explained. The `format` parameter benefits from both the schema description and the additional note about JSON round-trips, but the zip behavior is left unstated.

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 uses a specific verb and resource ('Export an Agent as a portable bundle') and names the exact endpoint. It also explicitly connects the output to `ethora-agents-import-v2`, which distinguishes it from sibling read tools like `ethora-agents-get-v2`.

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 clearly frames when to use export: to produce a portable bundle that can be fed back into the import tool to recreate an Agent in another App/tenant. It does not explicitly list exclusions or alternatives like clone/get, but the migration/backup context is clear.

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