list-cases

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

No annotations are provided, so the description is the sole source of behavioral info. It conveys a read operation with search/filtering, but lacks details on pagination limits, rate limits, or what happens with invalid queries. The minimal info is adequate but not comprehensive.

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, front-loaded sentence with 8 words, containing no fluff. Every term is necessary and directly conveys the tool's functionality.

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?

The tool has 4 optional parameters and no output schema. The description covers the core action (listing with search/filtering) but does not hint at return format, default sorting, or pagination behavior. While the schema covers parameters, the description could better round out context.

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%, with each parameter described in the schema. The description adds little beyond the schema: 'search and filtering' is already implied by the query parameter. No additional semantics or examples are provided, so the description adds marginal value.

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 Datadog Case Management cases with search and filtering' uses a specific verb ('List') and resource ('Datadog Case Management cases'), clearly distinguishing it from siblings like 'get-case' (single case) and 'create-case'.

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 implies usage for retrieving multiple cases, but does not provide explicit guidance on when to use this tool versus alternatives like 'get-case' or other list tools. No exclusion criteria or context given.

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