growsurf_create_mobile_participant_token

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

Annotations indicate readOnlyHint=false and destructiveHint=false, but the description adds context about 'trusted direct enrollment' and the risk of misuse for public apps. However, it does not disclose detailed side effects, permissions, or rate limits, so only partial transparency beyond the 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?

Two concise sentences that front-load the main action, then add a crucial warning and targeting logic. Every sentence earns its place, no 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?

For a tool with 11 parameters and an output schema, the description leaves many parameters unexplained (email, lastName, metadata, etc.). It does not mention how token creation interacts with the output or whether any preconditions exist. The warning about affiliate review is useful but the overall context is incomplete.

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 only 18%, so the description needs to compensate. It adds meaning for campaignId (default behavior) and isAffiliate (trusted enrollment context), but does not explain the other 9 parameters (email, firstName, etc.). It adds some value but not sufficient for the low coverage.

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 verb and resource: 'Create or fetch a participant, then create a participant-scoped mobile SDK token.' It distinguishes itself from siblings by mentioning the token scope and the GrowSurf REST endpoint, and notes the campaign targeting behavior. No confusion about what it does.

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 a clear warning: do not use for public application when affiliate review is required, which helps decide when to avoid it. It also implies when to use it (trusted direct enrollment). It does not explicitly name alternative tools, but the warning and context are helpful.

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