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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive hints, lowering the bar. The description adds useful behavior: format=json returns the bundle object directly, include selects sections, and the result feeds import. It leaves format=zip behavior unspecified, but this is a minor gap given the strong 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?

Three focused sentences with the core purpose front-loaded, followed by format behavior and import workflow guidance. No filler, no restatement of schema fields.

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 read-only export tool with rich annotations, the description covers the essentials: endpoint, format effect, include usage, and the downstream import step. The only missing items are the default include sections and what zip format returns, which would be useful given the absent output schema.

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 documents appId and include but leaves format with only an enum. The description adds real semantics by explaining that format=json returns the bundle object directly and by giving a concrete include example, compensating for the undocumented format behavior. appId's B2B-mode nuance remains in the schema, which is acceptable.

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 ('Export'), a specific resource ('App'), and a concrete deliverable ('portable bundle'), along with the exact endpoint. The explicit reference to ethora-app-import-v2 distinguishes this from the import counterpart and other app-related tools.

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 workflow context by directing the agent to feed the result to ethora-app-import-v2, establishing when this tool is needed. The schema adds appId context for B2B mode. However, it does not explicitly state when not to use it or contrast it with agent-level export tools.

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