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

Discloses return behavior (null when not linked) and precondition (requires project context), complementing the readOnlyHint annotation. No contradiction with read-only nature.

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?

Two focused sentences with no filler. Main purpose is front-loaded, followed by usage guidance and edge-case behavior.

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?

Covers purpose, usage, edge case (null), and prerequisite (project context). No output schema exists, so no return structure explanation is needed. Complete for a simple getter.

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 already describes testCaseId as 'Public Id (Guid) of the test case' with 100% coverage; the description does not add extra parameter semantics beyond that, but also does not omit anything.

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?

States the specific resource (request contract of spec endpoint linked to test case) and enumerates contents (header parameters, request body schema/example, response schemas per status). Clearly distinguishes from guessing, implying a non-guessing alternative.

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?

Explicitly instructs to use it for writing assertions that match the contract instead of guessing, and notes the null return condition for unlinked cases, providing concrete when-to-use guidance.

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