MCP Datadog Server

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

No annotations are provided, so the description carries full burden. It implies a read operation ('Fetch') but doesn't disclose critical behavioral traits: whether authentication is required, rate limits, error conditions, or what happens if the token is invalid. For a tool with zero annotation coverage, this is a significant gap in behavioral disclosure.

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, efficient sentence that front-loads the key action and resource. Every word earns its place: 'Fetch' (verb), 'existing shared dashboard's sharing metadata' (resource), 'associated with the specified token' (context). There is zero waste or redundancy.

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's complexity (fetching sharing metadata), lack of annotations, no output schema, and 0 parameters, the description is incomplete. It doesn't explain what the return value looks like (e.g., metadata structure), authentication requirements, or error handling. For a tool that likely returns structured data about sharing, this leaves the agent with insufficient information to use it effectively.

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 tool has 0 parameters with 100% schema description coverage (empty schema). The description adds context by mentioning 'the specified token,' which suggests a token is involved, but since there are no parameters, this might imply the token is handled elsewhere (e.g., in authentication). With no parameters, the baseline is 4, as the description provides adequate context for a parameterless tool.

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') and resource ('an existing shared dashboard's sharing metadata'), specifying what the tool does. It distinguishes from general dashboard retrieval tools by focusing on sharing metadata associated with a token. However, it doesn't explicitly differentiate from sibling tools like 'get_dashboard_public_invitation' which might handle similar sharing-related data.

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 minimal guidance, mentioning 'associated with the specified token' which implies a prerequisite token is needed. However, it offers no explicit when-to-use guidance, no alternatives (like 'get_dashboard' for general dashboard data), and no context about when this tool is preferred over siblings. This leaves the agent with insufficient decision-making context.

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