Get Request Config

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

Annotations already declare readOnlyHint=true. The description adds value beyond that by disclosing the null-return behavior when no request exists and the project-context requirement. These are genuine behavioral traits an agent needs to know. It doesn't cover response format details, but for a simple single-parameter read tool the null case is the key behavior and it is disclosed.

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 with zero waste: the core purpose and return contents are front-loaded in sentence one, the null edge case and fallback tool in sentence two, and the context prerequisite in sentence three. Every sentence earns its place.

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 one required parameter, no output schema, and no nested objects, the description is complete: it states what is returned, enumerates the returned fields, discloses the null case, points to the corrective tool, and flags the context prerequisite. Nothing an agent needs to call it correctly is missing.

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% — the schema already documents testCaseId as 'Public Id (Guid) of the test case.' The description adds no parameter-specific meaning beyond the schema, so the baseline of 3 applies. The description's mention of the request configuration contents does not meaningfully clarify the single parameter.

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 the full request configuration of a test case') and enumerates exactly what is returned: method, URL, body, scripts, and headers with their ids. This precise scoping clearly distinguishes it from siblings like get_request_logs or list_test_cases without needing to inspect their schemas.

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 explicit edge-case guidance: 'Returns null when the case has no request yet — use set_test_case_request to create one,' which names an alternative tool and the condition that selects it. It also states the prerequisite 'Requires project context.' It stops short of a broader when-to-use vs. when-not-to-use discussion across the large sibling set, hence not a 5.

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