getResultsForCase

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

The description says 'Retrieves' indicating a read operation, but no annotations are present. It does not disclose any further behavioral traits such as required permissions, rate limits, or side effects. The description carries the full burden, and it falls short.

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 a single sentence in English and Japanese, which is concise and front-loaded with the purpose. However, it could be more informative without being longer. Still, it is efficient.

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?

Given no output schema and multiple sibling tools, the description lacks completeness. It does not mention pagination, filtering, or what the response contains. For a tool with 6 parameters and no output schema, more context is needed.

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 has 100% description coverage, so the schema already documents all parameters. The description adds no additional meaning beyond what is in the schema. Baseline is 3, and no extra value is provided.

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 it retrieves test results for a specific test case in a test run. The verb 'Retrieves' and resource are explicit. However, it does not differentiate from the sibling tool getResultsForRun, which might return results for the entire run, but the name itself implies per-case.

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?

No guidance on when to use this tool versus alternatives like getResultsForRun or addResultForCase. No prerequisites, context, or when-not-to-use advice is provided. The usage is implied but not explicitly stated.

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