create_checkpoint_invite

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

Annotations already signal this is a non-read-only, non-destructive mutation. The description adds 'short-lived,' which hints at expiration behavior, but it doesn't explain side effects, whether invitations persist, or how one_time affects behavior.

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?

A single sentence with no filler; the core action is front-loaded and readable. It is concise, though the brevity leaves out meaningful context.

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 tool with three undocumented parameters, no required fields, and no output schema, the description is under-specified. It leaves unclear what 'root' refers to, how expiry is expressed, what one_time means, and what the tool returns.

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 0%, so the description should compensate for the three optional parameters. It doesn't explain 'root', the units or meaning of 'expires', or 'one_time'; only 'short-lived' loosely aligns with the expires 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?

Description states a specific verb ('Create') and resource ('checkpoint join link'), and 'short-lived' adds a useful qualifier. It is clear enough to distinguish from the sibling join_checkpoint, though it doesn't explicitly name that alternative.

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 given on when to create an invite versus using join_checkpoint, or whether prerequisites like an existing checkpoint or project binding are needed. Usage must be inferred entirely from the verb and sibling names.

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