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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds what the annotations cannot: an authentication prerequisite (techjobs.vn sign-in) and the meaning of the returned state fields, including that profile_missing explains what is empty in an incomplete profile.

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 auth requirement is front-loaded in the first sentence, followed by return contents and then the use case. It is dense but every clause carries information. The middle sentence packs many fields, which is slightly heavy but justified by the non-obvious state fields it names.

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?

With an output schema present the description need not document return shape, yet it usefully clarifies the less self-evident fields and the auth prerequisite, and it anchors the tool to register_as_referrer. For a zero-parameter read tool this is close to complete; only explicit exclusion guidance is missing.

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 there is no parameter semantics to explain and the baseline of 4 applies. The description correctly spends no space on arguments and instead describes the returned content.

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 verb and resource (lists referrer registrations) and scopes it to the signed-in user, then enumerates the exact fields returned (work email, company, verification click, approval, request email destination, profile completeness). It is clearly distinguishable from register_as_referrer, which it references as the write-side counterpart.

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?

It gives concrete when-to-use guidance: check whether register_as_referrer finished, and do so before asking for requests. That routes the agent relative to two siblings. It stops short of saying when NOT to use it or explicitly naming list_referrer_requests as the alternative, so it falls just short of the top band.

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