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

With no annotations, the description carries the full burden, and it does disclose a meaningful behavioral trait: results are metadata only, with no private messages or gift notes. It does not state whether the call is safe/read-only (implied by "List"), whether results are ordered, or what a page contains.

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, both load-bearing: the first establishes scope and excludes private content, the second explains pagination. Nothing is redundant and the scoping caveat is front-loaded.

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 two-parameter, no-annotation, no-output-schema list tool this is roughly adequate, but the description never sketches what the returned metadata contains or what an empty/terminal page looks like, leaving the agent to discover the response shape empirically. It also omits the limit default/cap that governs page size.

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 0%, so both parameters rely on the description. It usefully explains that pagination works by feeding the returned nextCursor back into cursor, which the schema cannot convey since there is no output schema. However, the limit parameter (default 50, max 100) gets no mention, and the switch from "nextCursor" to "cursor" naming could confuse an agent reading only the description.

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?

"List gifts sent to you" gives a specific verb and resource, and the parenthetical scope note distinguishes it from write operations like gift/gift_potion. The contrast with the sibling sent_gifts (gifts you sent) is implied by "sent to you" rather than stated, so it falls just short of full sibling differentiation.

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?

Usage is implied by the inbox framing rather than stated: an agent can infer this is the read path for received gifts vs. sent_gifts. There is no explicit "use this when" statement, no mention of when the mailbox is empty, and no named alternative.

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