permission_sets_get_assignments

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

Without annotations, the description compensates by disclosing key behaviors: it provides a caching duration of 15 minutes and confirms pagination support. It implies read-only operation but does not explicitly state it.

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 and well-structured: a clear one-sentence summary, followed by bulleted workflow tips and common use cases. No redundant text; every part serves a purpose.

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?

For a read operation with 3 parameters and no output schema, the description covers purpose, usage tips, caching, and pagination. It could mention the structure of returned data but is otherwise complete.

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 covers all parameters, but the description adds value with concrete usage examples (e.g., { 'id': '...', 'start': 0, 'limit': 50 }). This helps users understand how to apply the parameters in practice.

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 retrieves permission set assignments, specifying the action (get) and resource (permission set assignments). This distinguishes it from sibling tools like permission_sets_get (fetches a permission set) and permission_sets_list (lists all permission sets).

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 includes workflow tips like 'Shows all users with this permission set' and 'Use pagination for permission sets with many users', along with common use cases and example JSON. However, it does not explicitly state when not to use this tool or mention alternatives.

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