get-monitors

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

No annotations are provided, so the description must disclose behavioral traits. It states it's a list/filter operation, implying read-only, but does not mention pagination, rate limits, auth needs, or the limit parameter's default behavior. Adds some context but not enough.

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?

Four sentences with no redundancy. Front-loaded with purpose, then usage examples, then filtering details, then alternative. Efficient.

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 list tool with 4 parameters and no output schema or annotations, the description covers purpose and some parameters but omits important details like pagination and default limit. Could be more complete but is functional.

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 0% description coverage. The description explains groupStates values and tags usage, but does not clarify the difference between 'tags' and 'monitorTags', nor the 'limit' parameter. This leaves 2 out of 4 parameters under-explained.

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 it lists Datadog monitors with filtering, and provides example queries. It distinguishes from sibling 'get-monitor' which is for single monitor details.

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?

Gives explicit examples of when to use it ('show alerting monitors') and explicitly mentions the alternative for single monitor details. However, it does not cover all possible alternatives from the sibling list, but it covers the most relevant one.

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