GetCdsUnitTest

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

The description indicates a read operation but provides no additional behavioral details such as error handling, permissions, or data freshness. With no annotations, the description carries full burden, and it meets the minimum requirement without offering deeper insight.

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 concise sentence of 12 words, front-loaded with the action and resource, containing no extraneous information.

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 simple retrieval tool with one parameter and no output schema, the description is minimally complete. It specifies what is retrieved (status and result) but does not describe the output format or any error conditions, which could be improved for completeness.

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?

The schema description coverage is 100% for the single parameter 'run_id', so the baseline is 3. The description adds no extra meaning beyond the schema, merely restating that the run_id is for a previously started run.

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 'Retrieve CDS unit test run status and result for a previously started run_id', specifying the verb 'Retrieve' and the resource. However, it does not distinguish itself from sibling tools like GetCdsUnitTestResult and GetCdsUnitTestStatus, which may have overlapping functionality.

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 usage guidelines are provided. The description does not indicate when to use this tool versus alternatives like GetCdsUnitTestResult or GetCdsUnitTestStatus, leaving the agent without guidance on tool selection.

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