get_public_dashboard_params

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Get values', implying a read-only operation, but does not describe return format, error conditions, authentication requirements, or any side effects. Critical context for an agent is missing.

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, clear sentence with no superfluous words. It front-loads the core purpose without any waste, making it easy to parse quickly.

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 absence of an output schema and annotations, the description is minimal. It conveys the essential read operation but lacks details on return values (e.g., whether it returns a single value or a list), error handling, or the relationship to public dashboard sharing. For a simple tool this might be acceptable, but completeness is only moderate.

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 description coverage is 0% (the top-level 'input' parameter lacks a description, though its sub-properties have brief descriptions like 'Public sharing UUID' and 'Parameter key slug'). The tool description does not elaborate on parameter semantics beyond what the schema provides, missing an opportunity to clarify the role of 'uuid' and 'param_key' in a public dashboard context.

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 action ('Get values'), the resource ('parameter in a publicly shared dashboard'), and the context ('from Metabase'). It is specific and unambiguous, but does not explicitly differentiate from sibling tools like 'get_public_dashboard_param_values' or 'search_public_dashboard_params', which might have overlapping functionality.

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 provides no guidance on when to use this tool versus its siblings (e.g., search_public_dashboard_params, get_public_dashboard_param_values). There is no mention of prerequisites, alternatives, or exclusions, leaving the agent to infer usage based solely on the tool name and brief description.

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