view_custom_query_dashboard

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

No annotations are provided, so the description carries the burden. 'View' clearly indicates a read-only operation, and the description adds what the user will see (rows, visualization, insight). It does not disclose behavior beyond that, such as whether the report must be previously saved or whether any side effects occur, but for a view operation this is minimally adequate.

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?

One concise sentence that front-loads the action and immediately specifies the object and output contents. There is no filler, repetition, or unnecessary detail.

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?

For a single-parameter read-only tool with no output schema, the description covers the core operation and expected content. It lacks explicit usage guidance and parameter semantics, but the low complexity keeps the definition reasonably complete.

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 schema description coverage at 0% and no parameter explanation in the description, report_id is only documented by its schema title and type. The description references 'a saved report' but does not add meaningful semantics about the identifier or how it should be obtained, so it fails to compensate for the schema gap.

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 a specific verb ('View') and names a distinct resource ('saved single-query custom_query report'), then enumerates what is returned: rows, chosen visualization, and a Claude-generated insight. This clearly differentiates it from siblings like view_report_builder_dashboard and get_report.

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 phrase 'saved single-query custom_query report' implies this tool is for viewing an existing report rather than building or running one. However, it does not explicitly state when to choose this over get_report or view_report_builder_dashboard, nor does it mention any exclusions.

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