datadog_list_dashboards

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It merely states 'List Datadog dashboards,' omitting details about whether the list is paginated, what fields are returned, or any side effects. The existence of a 'filter_shared' parameter is not highlighted, missing an opportunity to clarify behavior.

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 at three words, leaving no room for waste. However, it could be slightly expanded to include a brief note on authentication or the optional filter parameter without sacrificing 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?

For a simple list tool, the description is adequate but incomplete. It does not mention the optional 'filter_shared' parameter or the expected output format, which would be helpful given no output schema is provided. The tool's simplicity keeps the score at 3.

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% with descriptions for all three parameters (api_key, app_key, filter_shared). The description adds no additional insight beyond what the schema already provides, so the baseline score 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 action ('List') and resource ('Datadog dashboards'). However, it does not differentiate from sibling tools like 'datadog_list_monitors' or 'datadog_list_events' beyond the resource name itself, which is already evident from the tool name.

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 versus alternatives such as 'datadog_get_monitor' or 'datadog_query_metrics'. There is no mention of prerequisites, contexts, or cases where one would prefer another tool.

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