MCP Datadog Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a read operation ('Get') but does not specify whether it retrieves a single framework or multiple, what authentication is required, or any rate limits. The lack of detail makes it inadequate for a tool with zero annotation coverage.

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 sentence 'Get a custom framework.', which is concise but under-specified rather than efficiently informative. It front-loads the core action but lacks necessary elaboration, making it more sparse than helpful.

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 (implied by 'cloud security management'), no annotations, no output schema, and 0 parameters, the description is incomplete. It fails to explain what a custom framework is, what data is returned, or how it fits into the security management context, leaving significant gaps for the 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 tool has 0 parameters with 100% schema description coverage, so the schema fully documents the absence of inputs. The description does not add parameter information, which is acceptable given the baseline of 4 for zero parameters, as no compensation is needed.

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 'Get a custom framework' restates the tool name with minimal elaboration, making it a tautology. It specifies the verb 'Get' and resource 'custom framework' but lacks detail on what a custom framework entails or how it differs from other frameworks, failing to distinguish from siblings like 'get_cloud_security_management_resource_filters'.

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. The description does not mention prerequisites, context, or exclusions, leaving the agent with no usage instructions. Sibling tools like 'create_cloud_security_management_custom_frameworks' and 'delete_cloud_security_management_custom_framework' exist, but no comparison is made.

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