datadog_monitor_list

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

Discloses read-only nature, output format (YAML), auto-pagination behavior (limit 0 or omitted fetches up to 10000), and distinguishes between tags and monitor_tags filters. No annotations, but description fully covers 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?

Extremely concise with no wasted words. Front-loaded with key action and resource, then necessary details in a clear progression.

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?

Complete for a list tool with 4 parameters and no output schema. Addresses all parameter meanings, alternative tools, output format, and pagination. No gaps.

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%, so baseline 3. Description adds value with examples for name and tags, explains the difference between tags and monitor_tags, and clarifies limit behavior, exceeding minimal requirements.

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?

Clearly states the tool lists Datadog monitors with optional name/tags filters, distinguishing it from siblings like datadog_monitor_search and datadog_monitor_get.

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?

Explicitly tells when to use this tool vs alternatives: use datadog_monitor_search for free-text/faceted queries, datadog_monitor_get for known numeric IDs. Provides clear context.

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