iranti

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively explains that this tool persists data across turns, sessions, and agents, and that it writes to shared entities when entityTargets are supplied. It mentions what gets stored (e.g., current_step, next_step) but doesn't cover potential side effects like rate limits, authentication needs, or error handling.

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 well-structured and front-loaded, with the first sentence stating the core purpose. Each subsequent sentence adds meaningful context without redundancy. It efficiently covers usage scenarios, comparisons to alternatives, and behavioral implications in a compact form.

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 complex tool with 13 parameters and no output schema, the description does a good job explaining the tool's role and when to use it. However, it lacks details on return values or error conditions, which would be helpful given the tool's mutation nature and absence of annotations. The description compensates well but doesn't fully address all contextual gaps.

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 description coverage is 100%, so the schema documents all parameters thoroughly. The description adds value by explaining the overall purpose of checkpointing and hinting at how parameters like entityTargets affect behavior ('writes canonical shared state... to those entities for handoff'), but doesn't provide additional syntax or format 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 clearly states the tool's purpose: 'Persist a shared progress checkpoint while you work.' It specifies the verb ('persist') and resource ('shared progress checkpoint'), and distinguishes it from siblings by calling it 'the strongest shared-RAM tool for active work' and contrasting with 'ad-hoc prose.'

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?

The description provides explicit guidance on when to use this tool: 'Use this at meaningful milestones' and 'prefer it over ad-hoc prose when you need another session or another agent to pick up where you left off.' It also mentions a specific alternative ('ad-hoc prose') and clarifies the tool's role relative to sibling tools by emphasizing its strength for active work handoff.

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