get_list_permissions

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Get role assignments,' implying a read-only operation, but does not elaborate on what role assignments are included (e.g., inherited permissions, current user vs. all users), the return format, or any side effects. This lack of detail leaves significant behavioral ambiguity.

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 gets straight to the point. It contains no unnecessary words or repetition, making it highly efficient.

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 simplicity (one parameter, no output schema, no annotations), the description is minimal but lacks essential context. It does not explain what the returned role assignments look like, whether inheritance is considered, or how to obtain the listId. This makes the tool less complete for an agent that needs to use it correctly without additional information.

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 input schema has one parameter, listId, with no description in the schema (0% coverage). The tool description does not compensate by explaining that listId identifies the target list. While the parameter name is self-explanatory, the description adds no meaning beyond the schema's type and requirement, failing to provide necessary context.

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 tool's function: 'Get role assignments for a list.' It uses a specific verb ('get') and resource ('role assignments for a list'), which effectively distinguishes it from sibling tools like get_list_item_permissions (which targets items) and list_role_definitions (which targets role definitions).

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 offers no guidance on when to use this tool versus alternatives. It does not mention when to prefer this over get_list_item_permissions or list_role_definitions, nor does it provide any exclusions or prerequisites. Usage is only implied by the tool's name and brief description.

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