Get Simulation Timeline

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

The description adds the behavioral trait 'chronological', which is useful context beyond the annotations. However, it does not disclose what constitutes 'events', whether the timeline is complete or filtered, or any details about return format or pagination. Given that the annotations already cover safety (readOnly, idempotent, non-destructive), this is adequate but not rich.

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, well-structured sentence that immediately conveys the action and the resource. It is front-loaded with the verb and has zero waste. This is exemplary conciseness for a simple read-only tool.

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 one parameter, no output schema, and good annotations. The description is minimally viable but leaves ambiguity about what events are included and how the timeline is structured. Since there is no output schema and many sibling tools, more detail about the nature of events would improve completeness, but the current level is acceptable for a straightforward read operation.

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 coverage is 100% as the only parameter, simulation_id, has a basic description. The tool description adds no additional meaning about the parameter—it does not explain how the ID is used, what formats are expected, or any constraints. Baseline 3 is appropriate since the schema carries the parameter documentation.

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 tool's function: 'Get a chronological timeline of events during the simulation.' The verb 'Get' plus the specific resource 'chronological timeline of events' is precise. This distinguishes it from siblings like get_simulation_actions (actions only) and simulation_history (broader history), making its purpose unambiguous.

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 is provided about when to use this tool versus alternatives such as mirofish_get_simulation_actions or mirofish_simulation_history. There is no mention of context, prerequisites, or exclusions. The description stands alone without helping the agent decide between similar read-only simulation tools.

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