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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is fully covered by structured data. The description adds one useful piece of context — the links target the 'full UniAffitti web app' (as opposed to an API or mobile surface) — but says nothing about whether sign-in is required for the links to resolve.

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?

A single sentence with zero filler, and the verb and destination are front-loaded before the enumeration of link categories. Nothing could be trimmed without losing information.

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?

An output schema exists, so the description need not explain return values, and it correctly spends its words on scope instead. For a zero-param read tool this is nearly complete; the only omission is whether the links are absolute or require an authenticated session.

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?

Zero parameters, so per the rubric the baseline is 4. There is no parameter surface for the description to clarify or for it to neglect.

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 ('Return') and resource ('deep links') and enumerates exactly which app areas are covered (account, listing creation, messages, requests, favorites). It is unambiguous what comes back, though it never distinguishes itself from structurally similar siblings like get_my_profile or list_my_messages, which cover the same domains with data rather than links.

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?

No when-to-use guidance and no exclusions. The critical ambiguity — this returns URLs to web pages, while get_my_profile / list_my_messages / list_my_requests return the underlying data — is left for the agent to infer, which is exactly the confusion that most needs resolving here.

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