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

Discloses snapshot fields (generation, reason, createdAt, drives, revertedFrom) and suggests diffing for evolution. Annotations already indicate read-only, so description adds behavioral context beyond annotations.

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?

Two concise sentences, no wasted words. Core purpose and usage hint are front-loaded.

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?

No output schema exists, but description lists snapshot fields adding some completeness. However, lacks description of the limit parameter, leaving a gap in understanding tool behavior.

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 only parameter 'limit' is not described at all in the description. With 0% schema description coverage, the description should have explained its purpose, but it didn't.

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?

Clearly states the tool lists soul revisions in newest-first order. Verb 'list' and resource 'soul revisions' are explicit. Distinguishes from siblings by focusing on soul mutation 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?

Implied usage for reviewing soul mutation history, but no explicit guidance on when to use versus alternatives like record_drives_drift or other list tools.

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