create_execution

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

Annotations indicate read/write, non-destructive, non-idempotent behavior. The description adds useful context: it aggregates several entity types, is a top-level container, is not a single run, and returns the new execution ID. It does not detail all side effects such as relationship behavior, but the essence is covered.

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 just three sentences, all informative and sequential: definition, contrast with sibling, follow-up actions. It wastes no words and front-loads the most important disambiguating 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?

The description is complete for a creation tool: it defines the resource, explains its role in relation to test collections, lists the sibling tools needed to fully assemble the execution, and states the return value. An agent has enough context to call this correctly even without an example.

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 every parameter is documented in the schema. The description adds no specific parameter semantics beyond the returned ID. According to the rubric, a high-coverage schema grants a baseline 3.

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 the resource ('Manual Test Execution', the top-level container on the Executions page) and what it aggregates. It explicitly differentiates this from Test Collection, making the tool's role unambiguous even among many siblings.

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?

It explicitly tells the agent when to use this tool vs create_test_collection, and names the follow-up add_* tools needed to populate it. This leaves no ambiguity about the workflow or alternatives.

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