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

With no annotations, the description carries the transparency burden. It discloses that the server re-simulates the trace, follows the verified path, freezes the session at the trace's at_tick, and applies the same 10-second budget as trace verification. This is meaningful behavioral detail beyond the schema.

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 first sentence is tightly packed and front-loaded, and the budget note is useful. However, the final rhetorical question, 'What happens just past the tick where they stopped looking?' adds no operational value for an agent selecting or invoking the 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?

For a single-parameter tool with no output schema, the description covers the operation, purpose, mechanism, and a key timeout constraint. It leaves minor gaps around exact return shape and failure behavior, but the agent has enough to invoke it correctly.

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 already fully documents the single required trace_id parameter, so the description does not need to add much. It implicitly associates the trace_id with the 'existing trace,' but adds no new format or usage details beyond the schema.

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 opens with a specific verb and resource: 'Fork a live flock session from an existing trace.' It explains the mechanism, mentions the at_tick target, and distinguishes itself from ordinary flock creation by emphasizing continuation from a verified trace.

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 clearly states the intended use case: continue where the author stopped by re-simulating an existing trace. It does not explicitly name alternatives such as flock_create for blank sessions, so it stops short of full when-not guidance.

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