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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description does add real value beyond that by listing the accepted read scopes and warning that human-written text arrives in untrusted_fields and must never be treated as instructions. It still never explains what the returned status actually contains or whether missing/deleted links error out.

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 short sentences, front-loaded, with no filler. The opening sentence is wasted text because it merely repeats the title, but the remaining scope list and untrusted-fields warning are dense and useful.

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?

Complexity is low (one required param, read-only, closed-world, no output schema), and the description does cover auth and the untrusted-text handling contract. However, it omits the semantics of the returned state and the identifier format, which are the two things an agent most needs to call this correctly.

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 coverage is 0% for the single parameter, so the schema only says link_id is a non-empty string. The description says nothing about whether link_id is a numeric ID, a slug, or an opaque token, nor where an agent obtains one, so it fails to compensate for the coverage gap.

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 first sentence, "Get where a link I made stands," is verbatim the tool title, so the description adds no new statement of purpose. "Where a link stands" is never defined (status? state? expiry?), and with many sibling tools involving links (get_paylink, get_cancel_link, get_checkout_link, get_file_view_link, get_upload_link, revoke_link), an agent cannot tell which link type this covers.

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?

There is no guidance on when to choose get_link over the numerous link-related siblings, no prerequisites beyond the scope list, and no exclusions. The only routing-adjacent information is the read-scope requirement, which is authorization rather than usage guidance.

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