List Test Data Sets

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

Annotations already declare readOnlyHint=true, and the description adds useful behavioral detail: the list returns 'names and row counts,' while the dataSetId variant returns 'columns and rows.' It also discloses the project-context requirement. It stops short of covering pagination caps or error behavior, but those are partially visible in the schema.

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?

Two sentences with no filler. The main action and return contents are front-loaded, the drill-down variant is stated efficiently, and the prerequisite is appended in a short clause.

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 read-only list tool with a fully documented schema, the description covers the output shape, the single-set mode, and the context prerequisite. It does not explicitly say testSuiteId is required for listing, but the schema states that, so the description is sufficiently complete.

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 description coverage is 100%, so all four parameters are already documented. The description adds a little extra meaning by clarifying the dataSetId mode includes columns and rows, but it does not meaningfully expand on skip/take/testSuiteId beyond what the schema already states.

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 states a specific verb and resource: 'List the data sets of a test suite' and clarifies what those are ('the tables that drive data-driven runs'). It also distinguishes the drill-down mode via dataSetId, making it clear this is about data sets, not test suites or other sibling resources.

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 clear usage context: list all data sets of a suite, or pass dataSetId to retrieve one full set. It also states a prerequisite ('Requires project context'). It does not explicitly contrast with alternatives like get_test_suite or list_test_suites, but the intended use is unambiguous.

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