list_ci_tests

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

No annotations are provided, so the description carries full burden. It states 'list', implying a read-only operation, but does not disclose pagination behavior, rate limits, authentication needs, or any side effects. The presence of pagination parameters (page_limit, page_cursor) is not explained.

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 exceptionally concise: two sentences, no filler. The first sentence states purpose and the second provides concrete use cases, ensuring key information is front-loaded.

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 has 6 parameters and no output schema, the description covers purpose and partial parameter semantics but lacks behavioral details like pagination, default sorting, and the structure of returned data, making it adequate but not thorough.

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?

With 0% schema description coverage, the description partially compensates by mentioning 'filter by query, time range', which maps to filter_query, filter_from, filter_to. However, the remaining three parameters (page_limit, page_cursor, sort) are not explained, leaving gaps in understanding.

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?

Description clearly states the action (list) and resource (CI test events from Datadog CI Visibility) and provides example queries like 'show failed tests', but does not explicitly distinguish from the sibling tool 'search_ci_test_events', which serves a similar purpose.

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 gives example use cases ('show failed tests', 'test results for service X'), implying when to use the tool, but lacks explicit guidance on when not to use it or how it differs from alternatives like 'search_ci_test_events'.

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