get_test_run_results

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

Annotations declare readOnlyHint=true, which description aligns with. Description adds details: paginated endpoint, per-item multiple executions, onlyLastExecutions filter, and exact return structure. No contradictions, and enriches beyond 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?

Three sentences cover purpose, key parameter, and return shape. No redundant words. Concise and well-structured.

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?

No output schema, but description details the return object fields. Covers pagination, API defaults, and filtering. Lacks explicit pagination iteration guidance, but adequate given tool simplicity.

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 clear descriptions. Description adds context: explains why onlyLastExecutions is useful (multiple executions per item) and describes return structure. Provides extra meaning beyond schema.

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 verb 'Page through' and the resource 'execution results of a Zephyr Scale test run'. It distinguishes the paginated endpoint from the deprecated non-paginated variant, making the tool's purpose unambiguous.

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?

Mentions the deprecated non-paginated variant, implying this is the correct paginated tool. Explains the onlyLastExecutions parameter usage. However, lacks explicit when-to-use vs siblings like get_test_run or get_latest_result_for_test_case.

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