preview_list_item_permission_update

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

The word 'Preview' conveys that the tool does not apply changes, which is a key behavioral trait. However, the description does not disclose what the preview returns, whether it validates permissions, or any side effects. With no annotations provided, the description only partially covers transparency.

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 that is front-loaded with the action and resource. It contains no filler or redundant information, 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?

Given the tool's complexity (permission changes with nested structure), the description is too minimal. It omits the relationship to the corresponding apply tool, what the preview output looks like, and any context about 'high-risk' changes. The lack of an output schema and annotations increases the need for a richer description, which is absent.

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 description makes no reference to the three parameters (listId, itemId, changes). Schema description coverage is 0%, and the description does not compensate by explaining the purpose or structure of the changes array, actions, or principals. The tool name and schema properties hint at meaning, but the description adds no semantic value.

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 identifies the action ('Preview') and the resource ('permission changes for one list item'). It distinguishes this from sibling tools like apply_list_item_permission_update (which applies rather than previews) and preview_list_permission_update (which targets list-level rather than item-level permissions).

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 explicit guidance on when to use this tool versus alternatives. It does not mention that this is a dry-run before applying changes nor that apply_list_item_permission_update should follow, nor does it distinguish from list-level previews. Usage is only implied by the word 'Preview'.

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