Export Dashboard JSON

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

Annotations already declare readOnly, idempotent, non-destructive. Description adds that output is suitable for import, but doesn't disclose any potential edge cases, authentication needs, or limitations. Adds marginal behavioral context.

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 concise sentences, front-loaded with the main action. No redundant or extraneous information. Every sentence earns its place.

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?

Covers essential: what it does, why (backup/transfer), and what it returns (JSON for import). No detail on output schema, but given simple tool and existing annotations, it's adequate. Minor gap: no mention of validation or error handling.

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 100% with a single parameter (dashboardId) already described. Description repeats the parameter info without adding new meaning such as how to obtain the ID or format constraints. Baseline 3 due to high coverage.

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?

Clearly states it exports a dashboard as a portable JSON definition, with explicit purpose: backup or recreate in another controller. Distinguishes from siblings like appd_get_dashboard and appd_save_dashboard_file by focusing on portable JSON for reuse.

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?

Implies usage for backup or transfer, but lacks explicit when-to-use or when-not-to-use compared to sibling tools like appd_save_dashboard_file or appd_get_dashboard. No direct alternatives mentioned.

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