user_list_available_permissions

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

With no annotations, the description carries the burden. It does mention the return type and content (dictionary with descriptions and risk levels), which is useful. However, it doesn't disclose any side effects or permissions required; as it is a read-only listing, that is probably fine, but the lack of annotations means more clarity would be better. No contradiction.

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 concise, two sentences, with the main purpose in the first sentence and return details in the second. No fluff.

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 has no parameters and an output schema that likely details the structure, the description is adequate. It provides the purpose and return content. It doesn't mention filtering or pagination, but for a simple list tool, that might not be needed. Slight gap: no indication of when to use it vs alternatives, but that is covered under usage guidelines.

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?

There are 0 parameters, so the schema provides no parameter documentation. The description doesn't need to explain parameters, but it does describe what is returned. Since there are no params, a baseline of 4 is appropriate.

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 states a specific verb ('List') and resource ('all available permissions'), which is clear. However, it doesn't explicitly differentiate from sibling tools like user_analyze_user_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 implies it is used to list permissions, and the sibling list includes tools like user_analyze_user_permissions, but no explicit when-not-to-use or alternatives are provided. The context signals suggest it is a listing operation, so usage is somewhat clear but not explicit.

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