list_chat_response_tests_route

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that—no mention of pagination via cursor, default page size, or filtering behavior—so it contributes no behavioral context of its own.

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 single phrase is front-loaded and free of waste, but its brevity reflects under-specification rather than efficiency. There is no structure beyond the bare title-like statement.

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 listing endpoint with 8 optional filtering/pagination parameters and no output schema, the description should at least hint at filtering, pagination, and result shape. It leaves the agent to reconstruct all of that from the schema alone.

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%, and all 8 parameters (types, cursor, search, page_size, sort_mode, sharing_mode, include_folders, parent_folder_id) are documented in the schema itself. The description adds no parameter meaning, so the baseline of 3 applies.

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 Agent Response Tests' names a verb and resource, so the purpose is identifiable, but it essentially restates the tool name and adds nothing about scope, filtering, or pagination. It does not distinguish this listing endpoint from sibling readers like get_agent_response_test_route or get_agent_response_tests_summaries_route.

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?

There is no guidance on when to use this tool versus alternatives such as get_agent_response_tests_summaries_route, list_test_invocations_route, or the folder/test read endpoints. The agent must infer usage entirely from the name.

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