resume_project

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

No annotations provided, but description fully discloses side effects ('Reads from event log and/or snapshot store. Does not modify data.') and clarifies behavior (snapshot vs event replay).

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?

Five sentences with no redundancy. First sentence states purpose, second adds usage context, third lists side effects. Efficient and well-structured.

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 all parameters have defaults and no output schema is provided, the description sufficiently covers purpose, usage, and side effects. Lacks discussion of failure modes or permissions, but overall adequate for the tool's simplicity.

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 provides full descriptions for all 3 parameters, so baseline is 3. Description adds little beyond schema defaults; it frames parameters via context (snapshot vs events) but does not detail each parameter.

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?

Clear verb 'resume' and specific resource 'project state' with explicit mention of source (snapshot or event history). Differentiates from sibling resume_with_intent by focusing on full state reconstruction including tasks, sessions, and memory.

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?

Explicitly states when to use: after restart or for multi-agent collaboration. Does not specify alternatives or when-not-to-use, but the context is clear enough.

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