nexus_start_age_verification_appeal_flow

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

Annotations already mark readOnlyHint=false, and the description reinforces this by calling it an ACTION. It adds useful context that initiating an appeal session has state-changing effects and that the returned URL must be opened to continue.

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 short sentences front-load the action, then state the side effect and return handling. There is no filler or redundancy.

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 zero-parameter action with an output schema, the description covers what the tool does, what it returns, and what to do next. It is complete enough for an agent to invoke and process the result.

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?

The tool takes zero parameters, so the input schema fully covers inputs. The description's mention of 'the current user' clarifies the implicit identity context.

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 names a specific action ('Start the age verification appeal flow for the current user') and identifies it as v2 GraphQL. It is clear enough to separate from read tools, but it does not explicitly contrast with the sibling nexus_start_age_verification_flow.

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?

No guidance is provided on when the appeal flow should be started instead of the basic verification flow, or what conditions trigger an appeal. The only hint is 'This is an ACTION, not a read,' which is a behavioral warning rather than selection guidance.

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