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

The description adds behavioral context beyond annotations: it's a mutation requiring business permission checks, with restrictions for FREE businesses, and a prerequisite call to check_business_tool_access. It also mentions showing warnings. Annotations already indicate not read-only, but description enriches the behavioral model.

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 four sentences, front-loaded with the action, and includes necessary prerequisites. It is not excessively verbose, though could be slightly more concise by merging related instructions.

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?

The description covers the workflow: check permissions, call check_business_tool_access, show warnings, and conditionally proceed. It is complete given the tool's complexity, though it omits success/failure behavior and return value details (no output schema).

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?

With 0% schema coverage, the description bears full burden for parameter explanations, but it only mentions 'by email' and does not clarify the participants array structure, the role of subscriptionObjectId, or the purpose of communityId and challengeId. This leaves the agent with insufficient semantics.

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 'Add participants to a challenge by email,' which is a specific verb+resource. It distinguishes from siblings like remove_challenge_participants and list_challenge_participants by focusing on adding participants.

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 provides explicit usage guidance: check business permissions, FREE businesses cannot use, call check_business_tool_access before collecting inputs, show warnings, and never proceed when blocked. However, it does not explicitly mention alternatives or when to not use this tool over others.

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