get_dashboard_definition

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

The description discloses the return values (complete dashboard source, type, app context, owner, viewing URL), which is sufficient for a read-only operation. However, it does not mention potential error conditions or permission requirements, though for a simple getter this is mostly 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?

The description is a single sentence that efficiently conveys the tool's action and expected output without any superfluous words.

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?

The description covers the main return values, compensating for the lack of an output schema. It is sufficiently complete for a simple retrieval tool, though it omits details like how the source format differs or what URLs look like.

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?

The schema coverage is 100%, so the description does not need to add parameter details. It does not provide any additional meaning beyond the schema's descriptions (e.g., what 'name' refers to), but the schema itself is clear. Baseline score of 3 applies.

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 tool retrieves the raw definition of a specific dashboard, distinguishing it from sibling tools like list_dashboards (which lists) and create_dashboard (which creates). The verb 'Get' and the specific resource 'dashboard definition' make the purpose unambiguous.

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 description implies usage when needing the raw definition of a specific dashboard, but does not explicitly state when to use it versus alternatives or provide exclusions. There is no mention of alternatives like list_dashboards for listing or get_studio_topic for Studio topics.

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