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

Read-only hint is provided and the description is consistent with it. Description adds behavioral details like execution order and that a single-case retrieval includes request config, assertions, and response extractions, which are meaningful but not covered by annotations alone. No side effects or destructive actions are implied.

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 efficient and well-structured, covering purpose, alternatives, parameter relationships, and context requirements in three sentences without extraneous detail. Slightly verbose due to the parenthetical example, but all content is relevant and useful.

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 tool with no output schema, the description adequately explains the return type (list of test cases or full case details) and key behaviors like execution order and project context requirement. It leaves out explicit mention of pagination, but skip/take parameters are documented in the schema, so the description covers the essential context.

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 descriptions cover all parameters, but the description adds important semantics beyond schema, such as the mutual exclusivity of testCaseId and testSuiteId (testSuiteId not needed when testCaseId is given) and the execution-order nature. This enriches parameter understanding beyond the basic field 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 clearly states the tool lists test cases of a suite in execution order. It also distinguishes it from reorder_test_items by explicitly mentioning that alternative for changing order, making the 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?

Provides explicit guidance: use for browsing a suite's cases in order, and use reorder_test_items for changing order. Also clarifies conditional usage for a single test case via testCaseId and notes the requirement for project context, covering both when and when not to use.

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