Import Dashboard from JSON

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

Annotations indicate readOnlyHint=false and destructiveHint=false. Description adds that the original ID is always discarded and a new one is assigned, which is key behavioral info beyond annotations. No contradictions.

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?

No fluff: one sentence purpose, a paragraph on function and workflow, then args list. Well-structured and efficient.

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 inputs, workflow, and return value (new dashboard with new ID). No output schema, but description addresses it. Could be slightly more explicit about when to use vs siblings, but sufficient.

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 detailed descriptions. The description's 'Args' section largely repeats schema, adding minimal extra value. Baseline 3 is appropriate as schema carries the burden.

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 'Create a new dashboard from a JSON definition string' and explains it uses JSON output from export tools, distinguishing it from siblings like appd_create_dashboard (create from scratch) and appd_clone_dashboard (duplicate existing). Discarding original ID reinforces purpose.

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?

Describes typical workflow with export-edit-import, and accepts 'JSON output of appd_export_dashboard or any saved dashboard JSON file'. Provides usage context but does not explicitly compare with alternatives like appd_create_dashboard for when not to use.

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