get-fork-history

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

With no annotations, the description must fully disclose behavior. It implies a read-only operation but does not mention whether the history includes deleted sessions, the ordering (e.g., most recent first), or if access permissions are required. The short description leaves ambiguity about side effects and data freshness.

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 clear sentence with no wasted words. It conveys the core purpose efficiently. However, it could benefit from a brief structured overview of the return value or behavior.

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 lack of an output schema, the description should indicate what the returned history contains (e.g., session IDs, timestamps). It does not, leaving the agent uncertain about the data shape. For a tool with one parameter and no output schema, this is a notable gap.

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 single parameter 'limit' is fully documented in the schema with a description and default value. The tool description does not add any additional semantics beyond what the schema provides, which is acceptable given the high schema coverage (100%).

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 retrieves 'history of recently forked sessions', specifying both the action (get) and the resource (history of forked sessions). It distinguishes from sibling tools like 'record-fork' which creates forks, and 'get-similar-sessions' which retrieves similar sessions rather than fork history.

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 on when to use this tool versus alternatives like 'record-fork' or 'get-session-summary'. The description lacks context such as prerequisites, typical use cases, or exclusion criteria.

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