session-revisit

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

The description contradicts the 'readOnlyHint' annotation by stating it saves a linked child record (a write operation). This misleads the agent into thinking it's read-only. No disclosure of write behavior or side effects.

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 concise sentence. It is front-loaded with the action and includes essential context (requirement). No redundant phrases, but could be slightly more 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?

Missing details: no output schema, no explanation of return values or errors. The contradiction between description and annotations adds confusion. For a tool that creates a child record, more behavioral context is needed.

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?

With 0% schema description coverage, the description adds no meaning to parameters. sessionId and cwd are left unexplained. The phrase 'current providers/config' hints at possible configuration but does not clarify cwd role.

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 purpose: 'Re-run a persisted session's original question with the CURRENT providers/config and save a linked child record (parentId).' This distinguishes it from sibling tools like session-get (retrieval) or session-annotate (annotation) by focusing on re-running and saving.

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 explicit guidance on when to use this tool versus alternatives. The phrase 'Requires sessions.persist; advisory' mentions a prerequisite but does not clarify context or exclude conditions.

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