create_case_participant

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

With no annotations, the description must disclose behavior. It mentions creating a participant and adding users to case access control. But it lacks details on prerequisites (e.g., required permissions), side effects (e.g., triggering workflows), or whether the operation is reversible. The eTag auto-fetch is a helpful behavioral detail.

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 relatively concise with four sentences, each adding unique information. It is front-loaded with the primary purpose. While more details could be added, it does not contain unnecessary 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 complexity (7 parameters, nested objects, no output schema), the description covers the core functionality, eTag behavior, and access control implication. It lacks error handling or prerequisites (e.g., case ID format) but is reasonably complete for agent invocation.

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%, but the description adds significant value: for eTag it explains auto-fetch and performance benefit; for content it specifies the Data-Party schema; for participantRoleID it links to permissions; and for pageInstructions and sessionCredentials it provides detailed examples and modes. This exceeds what the schema alone provides.

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 creates a new participant in a Pega case with a specified role and participant information. It distinguishes from siblings like add_case_followers, update_participant, and delete_participant by focusing on creation and access control.

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?

Provides some usage guidance, such as the auto-fetch behavior for eTag and the option to provide it for faster execution. However, it does not explicitly contrast with alternative tools like add_case_followers or update_participant, leaving room for confusion on when to use each.

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