Create Permission Set

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

Annotations already indicate a non-read-only, non-destructive, idempotent operation. The description adds useful conceptual context ('extend a user's access without changing their profile') but does not disclose additional behavioral traits such as behavior on duplicate fullName, merge semantics, or failure modes. No contradiction with annotations.

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?

Three concise, purposeful sentences. The first states the core function, the second explains the conceptual value, and the third gives a use-case example. No redundancy or filler; effectively front-loaded.

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 high-complexity tool with 8 parameters, the description provides adequate context: what it creates, the permission categories, and a realistic use case. The schema and annotations cover the remaining details. Without an output schema, the description could mention return values, but this is not essential for a creation tool given rich structured data.

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 description coverage is 100%, so parameters are already fully documented. The description merely lists the same categories (object, field, Apex, user) without adding new meaning or syntax details beyond the schema. 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?

The description clearly states 'Creates a Permission Set' with a specific verb and resource, and enumerates the permission categories (object, field, Apex class, user). It distinguishes conceptually from profile changes, but does not explicitly differentiate from closely related sibling tools like sf_create_permission_set_group or sf_create_muting_permission_set.

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?

Explicit usage guidance is provided: 'Use when you need to grant specific permissions to a subset of users' with a concrete example. The statement 'without changing their profile' implies a when-not scenario, though it does not name alternative tools or explicitly exclude profile-level modifications.

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