Create Muting Permission Set

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

Annotations declare idempotentHint=true, readOnlyHint=false, destructiveHint=false. The description adds context that these sets 'remove specific permissions' and are used for exceptions, but does not discuss side effects such as duplicate handling, deploy requirements, or permission prerequisites. With annotations covering the safety profile, the description provides moderate added context.

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 two paragraphs: a clear purpose statement and a compact parameter list. It is front-loaded with the main idea and no filler.

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 simple create operation, the description explains the purpose and parameters. It lacks return value information, but no output schema exists and sibling tools suggest this is a metadata creation tool. Annotations provide idempotency and safety context, so the description is sufficiently 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?

Schema covers 100% of parameters with descriptions, and the description repeats the parameter names and meanings. It adds no new information beyond the schema, so baseline 3 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?

Description states 'Creates a Muting Permission Set that removes specific permissions from users in a Permission Set Group.' This is a specific verb+resource and functionally distinguishes it from sibling 'sf_create_permission_set' and 'sf_create_permission_set_group'.

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?

Explicitly says 'Use to create exceptions — e.g., a Permission Set Group grants broad access, and a Muting Permission Set removes a subset of that access for specific users.' This provides clear context for when to use, but does not name alternative tools or explicitly state when-not-to-use.

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