Skip Review item

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

Annotations already indicate a non-read-only, non-idempotent operation, and the description adds context like 'pending item' and 'owned review session'. However, it does not disclose what 'skip' means in terms of state changes (e.g., whether the item remains pending, moves to a later position, or can be undone).

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, front-loaded sentence with no wasted words. It immediately states the verb and object, making it easy to parse.

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?

The description is too minimal for a tool with two required parameters, no output schema, and a complex domain (review sessions). It omits crucial context about the effect of skipping, preconditions (e.g., session ownership and state), and how it differs from apply_review_action, making it risky for an agent to invoke correctly.

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 must compensate for parameter meaning. It does so only implicitly: 'review session' suggests session_id and 'pending item' suggests item_id, but it does not explicitly map or explain the parameters, nor does it clarify unusual schema definitions (e.g., item_id referencing session_id in 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 action ('skip') and the resource ('one pending item in an owned review session'). It is specific and unambiguous, but it does not explicitly differentiate from sibling tools like personal_os_apply_review_action, which might handle similar operations.

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 no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., session must be active) or contrast with related review actions such as apply_review_action or complete_review.

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