openpanel_duplicate_dashboard

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

No annotations are provided, so the description carries full burden. It fails to disclose whether the operation copies nested resources (charts/widgets), permission settings, or what error occurs if the source dashboard doesn't exist. The '[UNIFIED]' prefix adds no 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?

The description is a single sentence, but the '[UNIFIED]' prefix is metadata noise that reduces signal. It is appropriately front-loaded but too minimal given the lack of schema documentation—it sacrifices necessary detail for brevity.

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?

Given 4 undocumented parameters, no output schema, and no annotations, the description is incomplete. For a duplication operation, it should specify what exactly gets copied (widgets, layouts, permissions) and whether the duplicate remains in the same project.

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?

With 0% schema description coverage, the description must compensate but does not. While 'existing dashboard' implies the purpose of 'dashboard_id', it doesn't clarify 'site', 'project_id' scope, or that 'new_name' is required for the duplicate. No parameter formats or constraints are described.

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 clearly states the core action ('Create a copy') and target resource ('dashboard'). It implicitly distinguishes from siblings like 'openpanel_create_dashboard' by specifying 'copy of an existing' rather than creating new, though it could explicitly name the sibling for clarity.

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?

No guidance provided on when to use this tool versus alternatives like 'openpanel_create_dashboard' or 'openpanel_update_dashboard'. No prerequisites mentioned (e.g., need for existing dashboard_id).

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