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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds meaningful context beyond that: validation only, no enrollment or publication side effects, and no handling of raw memory or private conversations. It stops short of describing what a validation result contains, which matters since no output schema exists.

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 compact sentences with the validation-only constraint front-loaded. No filler, though the second sentence ('No raw memory or private conversations') is somewhat cryptic without elaboration.

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 a large nested schema, no parameter descriptions, and no output schema, the description is thin: it does not explain what validation checks are performed, what failures look like, or how the referralCode affects the preview. An agent could call it but could not predict its behavior on invalid input.

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 0% across three parameters with deeply nested objects, so the description carries the full burden. It gestures at 'profile' and 'context labels' but says nothing about the required fields, the context.inferredFields/sourceLabels structure, or the referralCode parameter, which is entirely unaddressed.

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?

States a specific verb (validate) and a specific resource (portable profile draft + private context labels), and the phrase 'without enrolling or publishing' implicitly distinguishes it from prepare_signup. It never names a sibling explicitly, so differentiation is inferential rather than stated.

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?

'without enrolling or publishing' implies this is the pre-flight check before an actual signup/publish step, which is a useful implicit cue. However, no explicit when-to-use/when-not, and no mention of why one would prefer this over assess_profile_context or prepare_signup.

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