get_dashboard_details

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

Annotations already mark this as read-only and idempotent. The description adds valuable behavioral nuance by disclosing truncation behavior for large dashboards, referencing fields like 'truncated', 'warning', and 'total_available'. This goes beyond the annotations and helps set expectations about response limits.

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 two sentences, front-loaded with the primary purpose, and the second sentence adds a concise usage hint and a relevant caveat. No wasted words; every sentence earns its place.

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?

For a simple read tool with an output schema and strong annotations, the description covers the essential context: what it returns and how truncation may affect large responses. The usage scenario is also stated. This is complete for the tool's complexity.

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 already provides full documentation for the only parameter, dashboard_id, with the description 'Dashboard ID from list_all_dashboards'. Since schema description coverage is 100%, the description does not need to add extra parameter semantics, and it doesn't. 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 states the tool's function: 'Get complete dashboard configuration and widgets.' The verb 'Get' and specific resource 'dashboard configuration and widgets' distinguish it from sibling tools like get_monitor_details or get_full_trace, which target different entities.

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 a clear use case: 'Use this when: need to see what's in a dashboard or copy its configuration.' It gives explicit when-to-use guidance, though it does not explicitly state when not to use it or mention alternatives. This is still clear context for the agent.

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