Open a saved dashboard

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds the behavioral constraint of requiring the +Validation feature and explains that the tool returns the full definition, which aligns with read-only intent. 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?

Two sentences conveying all necessary information with no redundant words. Front-loaded with the core action and result, then the prerequisite. Excellent conciseness.

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?

Despite no output schema, the description explains what the full definition contains (solution/source + pages + branding), which is sufficient for a read operation. Also notes the validation feature requirement, covering key contextual aspects.

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%, and the schema describes the 'id' parameter as 'the saved dashboard id from daxops_list_dashboards'. The description echoes this without adding new semantic detail, so baseline 3 is appropriate.

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 verb (Fetch) and resource (saved dashboard's full definition) with specifics on what is returned (solution/source + pages + branding). It distinguishes siblings: daxops_list_dashboards lists dashboards, daxops_save_dashboard saves, while this fetches one by id.

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 after listing dashboards (needs id from list_dashboards) and states a prerequisite ('Requires the +Validation feature'). It provides context for review/rebuild but lacks explicit when-not or alternative guidance beyond what's obvious.

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