emu_get_scenario_run_events

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

There are no annotations provided, so the description carries the full burden of disclosing behavior. It only says 'Get the event log' – it doesn't disclose whether this is a read-only operation (likely implied but not stated), whether it returns a large volume of events, whether pagination or filtering is supported, or whether events are ordered or sorted. Given the lack of annotations, more detail is needed about what the event log contains and how it behaves.

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, short sentence. It is appropriately sized for the tool's simplicity, with no fluff or redundant content. It is front-loaded with the verb 'Get' and states the resource clearly. Conciseness is excellent, though this does not compensate for gaps in other dimensions.

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 the tool's simplicity (one parameter, no output schema, no annotations), the description is minimal but arguably sufficient for a basic read operation. However, the context signals include 70+ sibling tools, suggesting a complex system where event logs might have different meanings across operations, call sessions, or CDR records. With no output schema and 0% schema description coverage, an agent needs more context about what the return format looks like, how the event log relates to scenario runs, and whether events are structured. This falls short of minimum viable for a tool in a large ecosystem.

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 input schema has one required parameter, 'id' of type string, with 0% schema description coverage. The description does not explain the semantics of the 'id' parameter beyond what the schema shows. With a single parameter and zero description coverage, the description should clarify whether 'id' refers to a scenario run ID, a unique identifier, and any expected format or constraints. The description adds no meaning beyond the schema's bare type declaration.

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 'Get the event log for a v2 scenario run' states a specific verb ('Get') and a resource ('event log for a v2 scenario run'), and it services a scenario-related domain. It differentiates from siblings like emu_get_scenario_run (which likely gets the run itself) by specifying the event log aspect, though the 'v2' qualifier is slightly odd without context. It is clear enough but not exemplary.

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 versus sibling tools like emu_get_scenario_run, emu_list_operation_runs, or emu_list_active_calls. It doesn't mention whether this tool is for a specific scenario run state, whether it pairs with emu_apply_scenario, or what distinguishes an event log from a run summary. The context signals include many sibling tools for scenarios and runs, but the description provides no usage context.

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