Export Agent

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

Annotations already indicate readOnly, idempotent, non-destructive behavior. The description adds useful behavioral context beyond annotations: format=json returns the bundle object directly)Skip and that the bundle can be fed to import for cross-tenant recreation. It does not fully describe the zip return behavior, but this is minor given the annotation coverage.

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 compact sentences, with the primary action and endpoint front-loaded, followed by the round-trip purpose and prerequisite sourcing. Every sentence earns its place with no filler.

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 simple export tool with no output schema, the description covers what the tool produces, how to consume it, and where to get the required identifier. It could mention the zip format behavior more explicitly, but the essential calling context is complete.

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 67%, and the description compensates by clarifying that the agent id comes from list/create tools and that json is the preferred format for MCP round-trips. It also reinforces the alias relationship between agentId and agentIdOrAddress via the schema description. This adds meaning above the raw schema.

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: 'Export an Agent as a portable bundle', with the exact endpoint and the round-trip use case. It distinguishes itself from sibling tools by explicitly naming ethora-agents-import-v2 as the counterpart that consumes the exported bundle.

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?

Provides clear guidance on when to use it: to export an agent and later recreate it in another App/tenant via import. It also tells the agent where to obtain the required id/address (from ethora-agents-list-v2 or ethora-agents-create-v2). It does not explicitly list exclusions versus get/clone, but the context is sufficient.

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