get_test_collection

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

Beyond the readOnly/idempotent annotations, the description adds crucial behavioral context: the executionId is the row's own ID and not a Manual Test Execution ID, so passing it to get_execution would fail. It also discloses the conditional nature of the tests array based on includeTestDetails. No contradiction with annotations.

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 long but dense with useful distinctions. It is front-loaded with the core action and resource, and every sentence conveys a worthwhile fact, though a few phrases are slightly redundant with the annotations.

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?

With no output schema, the description fully compensates by listing metadata, stats, and the tests array structure, including the crucial executionId caveat. The agent has everything needed to invoke the tool and interpret the result correctly.

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 the baseline is 3, but the description enriches parameter understanding by stating where collectionId comes from and clarifying that includeTestDetails controls the tests array. This adds value beyond the schema's property descriptions.

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 ('Get one Test Collection by UUID') and enumerates exactly what is returned. It explicitly distinguishes this tool from get_execution and list_test_collections, so an agent can reliably tell them apart.

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?

It gives explicit routing guidance: use list_test_collections to find collections, use get_execution/get_execution_cases for Manual Test Executions, and clarifies that executionId rows are not execution IDs. This is exemplary when-to-use versus alternative tools.

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