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

Beyond the annotations (readOnlyHint=false, destructiveHint=true, idempotentHint=false), the description discloses auth requirements and an important side effect the annotations cannot express: the candidate is notified that a referrer is looking at the request. It does not explain what happens on a conflicting claim or whether the action can be undone, so it stops short of full transparency.

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 prerequisites are front-loaded and every sentence carries information. The teletype fragment style ('Then mark_referral_request_referred once submitted, or release_referral_request / decline_referral_request.') is dense but slightly elliptical, and the trailing sentence listing siblings reads as notes rather than prose.

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 only one well-documented parameter, full annotations, and an output schema, the description covers the remaining gaps an agent needs: auth requirements, the notification side effect, and the correct next step in the referral lifecycle. Only failure/conflict behavior on an already-claimed request is unaddressed.

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 100% and the single parameter already points back to list_referrer_requests, so the schema carries the semantics. The description adds no further detail about the request_id format or validation bounds, which is acceptable at baseline but adds no value.

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 uses a specific verb and resource ('Takes an open referral request for the signed-in referrer') and scopes it to the caller's own account, which separates it from read-only siblings like list_referrer_requests. It does not explicitly contrast itself with the other lifecycle tools (release/decline/mark_referred), leaving that differentiation to the follow-up sentence.

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 states the prerequisites (techjobs.vn sign-in plus a verified referrer account) and the condition ('open referral request'), and it names the correct follow-on tools and when to use each. There is no explicit when-not-to-use, but the 'open' qualifier implies the request must be unclaimed, which covers the main misuse case.

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