List evaluation test sets

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It does not state that this is a read-only operation, what permissions are needed, whether results are paginated, or what the return shape looks like. The phrase 'standard harness' is cryptic and adds little actionable context.

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, compact sentence with no wasted words. It is front-loaded with the resource type. The brevity is appropriate for a list operation, though the sentence borders on under-specification rather than optimal conciseness.

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?

The tool has five optional parameters, no output schema, and no annotations. The description does not explain what a 'test set' contains, what the response looks like, or how authentication defaults interact. Given the complexity of the Power Platform environment and the number of sibling tools, this description is too thin to fully guide correct invocation.

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%, so the schema already documents all five parameters including their defaults and environment variable fallbacks. The description adds no additional parameter meaning beyond what the schema provides, so the baseline score of 3 is appropriate.

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 identifies the resource as 'test sets defined for the agent' and adds '(standard harness),' which gives a clear sense of what the tool returns. Combined with the title 'List evaluation test sets,' an agent can determine it lists test sets for an agent. However, it does not explicitly distinguish this from sibling tools like cs_get_test_set or cs_list_evaluation_runs.

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 provides no guidance on when to use this tool versus alternatives such as cs_get_test_set or cs_list_evaluation_runs. It merely states what the resource is, leaving the agent to infer usage context from the name alone.

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