preview_list_permission_update

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

With no annotations provided, the description carries the full burden. 'Preview' indicates a non-mutating dry-run, but the description does not disclose what the preview returns, whether it validates changes, or any safety implications. This is a significant gap for a preview tool.

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 sentence with no filler, making it efficient and front-loaded. However, the brevity sacrifices necessary detail, which is penalized under completeness rather than con conciseness.

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 tool has moderate complexity with nested objects in the changes parameter, no output schema, and no annotations. The description is too sparse to inform an agent how to correctly invoke the tool or interpret results.

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 schema has 0% description coverage, and the description only names 'permission changes' generally, offering minimal insight into the 'changes' structure (action, principalId, roleDefId) or the listId parameter. It fails to compensate for the schema's lack of descriptions.

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 uses the specific verb 'preview' and names the resource 'list permission changes', clearly stating what the tool does. It is distinguishable from sibling preview tools by focusing on permissions, though it doesn't explicitly reference the apply counterpart.

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 implies using this tool to preview permission changes before applying them, but does not explicitly state when to use it vs alternatives or provide exclusion criteria. The 'high-risk' adjective is suggestive but not actionable guidance.

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