emu_create_operation_run

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

No annotations are present, and the description does not mention side effects, return format, potential errors, or any behavior beyond 'execute'. It fails to describe what a synchronous drill does or what impact it has on the system.

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 extremely short, which is concise, but it omits essential information. It reads like a placeholder and does not front-load any useful context. The brevity is not an asset here because it fails to convey necessary semantics.

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?

With no output schema and no parameter details, the description is completely inadequate. An agent cannot determine what parameters to provide, what the operation does, or what to expect as a result. It is not complete enough for any practical use.

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?

Six parameters are defined in the schema but none are described in the description. With 0% schema coverage, the description must compensate, but it provides no meaning for 'id', 'kind', 'limit', 'eventIds', 'phoneNames', or 'publisherKinds'. This leaves the agent guessing about required input.

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 states a verb ('Execute') a resource ('operations drill'), but 'operations drill' is ambiguous and not differentiated from similar tools like emu_create_call_session or emu_apply_scenario. It doesn't clarify what an operation run entails or how it differs from related list/get tools.

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. Given the many sibling tools for operations, call sessions, and scenarios, the description provides no decision context or exclusions.

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