datadog_dashboard_get

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

The description indicates it is a read operation that returns data, but with no annotations, the burden is higher. It does not explicitly state lack of side effects, authentication needs, or rate limits. The mention of output format (YAML) is helpful but incomplete for full transparency.

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 very concise: three sentences that each add distinct value—purpose, output scope, and format reference. It is front-loaded and has no redundant information.

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 tool with one required parameter, the description covers the main points: what it does, the input type, and output format. It lacks details on error handling or authentication but is mostly complete given the low 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?

Since the schema description coverage is 100% (the single parameter 'dashboard_id' has a clear description with an example), the tool description adds no additional meaning. 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 action ('Fetch a single Datadog dashboard by id'), the resource ('dashboard'), and what is returned ('full definition including widgets'). It also implicitly distinguishes the tool from the sibling 'datadog_dashboard_list' which is for listing all dashboards.

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 like 'datadog_dashboard_list'. There are no hints about prerequisites or context that would help an agent decide between tools.

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