apex_export_app

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe, non-destructive operation. The description adds no additional behavioral context beyond stating that it exports a script; it does not mention side effects (e.g., writing to output_path) or limitations. This meets the baseline but adds nothing extra.

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 a single, front-loaded sentence: 'Export an app as SQL install script.' It contains no filler and immediately conveys the tool's purpose. It is appropriately sized for a simple tool, though perhaps too terse for broader context.

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?

The tool is simple, with only two parameters and strong annotations. The schema covers parameter details, and an output schema exists, so return values need not be described. The description could benefit from distinguishing it from apex_export_page, but given the other structured fields, the description is mostly adequate. A score of 4 reflects this balance.

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?

The input schema has 100% description coverage for both parameters (app_id and output_path), so the schema fully documents them. The description does not expand on parameter semantics, but given the complete schema, no additional explanation is needed. Baseline 3 is appropriate.

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 the specific verb 'Export' with the resource 'an app' and the output 'SQL install script.' This clearly distinguishes it from siblings like apex_export_page (which exports a single page) and other generative tools. The purpose is immediately clear.

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 provides no guidance on when to use this tool relative to its alternatives. It does not mention apex_export_page or any other sibling, nor does it specify prerequisites or exclusions. The name implies whole-app export, but the description itself lacks explicit usage direction.

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