get-dashboards

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

The description claims 'List all' but does not disclose that pagination (via 'count' and 'start' parameters) limits results, nor does it mention API access constraints or rate limits. With no annotations, the description carries full burden but fails to explain behavioral traits.

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 concise sentence that communicates the core purpose without any wasteful words.

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 tool has four parameters (including pagination), no output schema, and no annotations, the description is incomplete. It omits details about response format, pagination behavior, and authentication needs, leaving significant gaps for an agent.

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 has 100% description coverage for all four parameters, so baseline is 3. The description adds no additional meaning beyond the schema, not even a summary of the parameters.

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 'List all Datadog dashboards' uses a specific verb ('List') and resource ('Datadog dashboards'), clearly distinguishing it from sibling tools like 'get-dashboard' which retrieves a single dashboard.

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 alternative tools such as 'get-dashboard' for a single dashboard. It does not mention exclusions or prerequisites.

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