get_dashboard_metadata

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

With no annotations provided, the description must disclose behavioral traits, but it only states the action. There is no mention of whether the operation is read-only, any required permissions, rate limits, or data sensitivity.

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 with no extraneous words, making it concise. However, it is too brief to be fully informative, and there is no structure that aids scannability.

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 complexity of the sibling tools and the lack of an output schema, the description is insufficient. It does not explain what 'query metadata' entails, nor does it differentiate sufficiently from similar dashboard-related tools.

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 includes an 'id' parameter with a description 'Dashboard ID', but the tool description does not add any additional meaning beyond that. The description fails to compensate for the 0% schema coverage of the outer input object.

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 states a specific verb 'Get' and a resource 'dashboard query metadata', which distinguishes it from sibling tools like 'get_dashboard' that likely return full dashboard details. However, 'query metadata' is vague and could encompass multiple things.

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?

No guidance is provided on when to use this tool vs alternatives such as 'get_dashboard', 'get_card_metadata', or 'get_dashboard_tile'. The description does not clarify the specific use case or prerequisites.

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