openpanel_update_chart

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

No annotations provided, so description carries full burden. Mentions 'Update' implying mutation but fails to disclose error behavior (what if chart_id invalid?), whether updates are atomic, or what the operation returns. Does not clarify if omitted optional fields (title, chart_type, events) are unchanged or reset.

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?

Single sentence is appropriately brief, but '[UNIFIED]' prefix wastes tokens without adding semantic value. Front-loading is acceptable though content is under-specified rather than efficiently concise.

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?

Inadequate for a 7-parameter update operation with no output schema and 0% input schema coverage. Missing: identifier hierarchy explanation, valid values for chart_type/events, error conditions, and return value description. Tool requires significant inference from the agent.

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 has 0% description coverage, but the description adds zero parameter context. No explanation of the hierarchical identifiers (site/project_id/dashboard_id/chart_id), valid chart_type values, or the 'events' parameter format (JSON string? comma-separated?). Completely fails to compensate for undocumented schema.

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 specific verb 'Update' and resource 'chart configuration', distinguishing from sibling tools like openpanel_add_chart and openpanel_delete_chart. However, '[UNIFIED]' prefix is metadata noise and 'chart configuration' lacks domain context (analytics dashboards vs other chart types).

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 no guidance on when to use this versus openpanel_add_chart or openpanel_create_dashboard. Does not mention prerequisite steps (e.g., needing valid chart_id from openpanel_get_dashboard or list operations) or partial vs full update semantics.

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