get_dashboard_parameters

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

No annotations are present, so the description bears the full burden. It indicates a read operation, implying no destructive side effects, but does not mention authorization needs, rate limits, or what happens if the dashboard does not exist. For a simple getter, this is adequate but minimal.

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 extremely concise, consisting of a single phrase that efficiently conveys the tool's purpose. No redundant words or sentences are present.

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 the tool's simplicity (single parameter, no nested objects, no output schema), the description covers the essential functionality: it returns 'current dashboard parameter values and widget mappings'. This is sufficient for an agent to understand the tool's role, though more detail on the output structure would strengthen completeness.

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 input schema provides 100% coverage with a clear description for the sole parameter 'dashboardId' ('ID of the dashboard'). The tool description adds no further semantics beyond the schema, so a baseline of 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 specifies the tool's function: retrieving current dashboard parameter values and widget mappings. It uses a specific verb ('Get') and resource ('dashboard parameter values and widget mappings'), distinguishing it from sibling tools like 'get_dashboard' or 'get_widget_parameter_mappings'.

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 for accessing current parameter values and mappings, but lacks explicit guidance on when to prefer this tool over alternatives such as 'get_widget_parameter_mappings' or 'get_dashboard'. No when-not-to-use or prerequisites are provided.

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