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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds the authentication prerequisite and a negative scope statement not present in structured fields. It does not describe the return shape (e.g., whether VIP status is a boolean or expiry date), which would complete the picture.

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 sentences, front-loaded with what is checked, followed by the login requirement and scope caveat. Every clause earns its place and nothing is redundant with the annotations.

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 read tool whose annotations cover safety, the description supplies the important remaining context: authentication requirement and what is not returned. The only gap is the absence of any indication of the response shape or behavior when not logged in, since there is 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?

The tool takes zero parameters, so the schema baseline of 4 applies and there are no parameter semantics to add or omit.

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 ('Check') and two precise resources (connected account, active VIP membership), making the scope unambiguous. The clause 'this does not expose personal profile fields' explicitly separates it from sibling profile tools like get_candidate_profile and get_grant_profile.

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?

Gives the key precondition ('Login is required') and an explicit exclusion (no personal profile fields), which implicitly routes agents to the profile siblings for that data. It stops short of naming an alternative tool directly or saying when not to call it.

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