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

With no annotations, the description carries the full burden and discloses almost no behavior: it doesn't say whether KBUX is deducted from the caller's balance, whether the transfer is reversible, whether requestId is an idempotency key, or what happens on failure or insufficient funds. "Requires a UUID requestId" restates the schema's format rather than explaining its role, so the only real inference available is that this is a value-moving mutation.

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, front-loaded sentences with no filler: the action and target set come first, the hard requirement second. Nothing is redundant or padded.

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 three-required-parameter, annotations-free, output-schema-free currency transfer, the description is only minimally sufficient. It establishes what the tool does and one prerequisite, but leaves the amount parameter, the caller-facing consequences (balance debit, irreversibility), and any success/error behavior undocumented.

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 the description needed to compensate. It does identify requestId as a required UUID (though the schema already declares format=uuid) and implies messageId from "public chat message, sticky, or family ping", but `amount` — a bounded integer from 1 to 2147483647 — is never mentioned or explained, leaving one of three required params with no semantics anywhere.

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 gives a specific verb ("Tip") plus the unit ("KBUX") and a clear set of target resources (public chat message, sticky, family ping), so the agent knows exactly what action it performs. It falls short of a 5 because the sibling list contains four near-identical tools (codelab_tip, library_tip, muse_tip, workshop_tip) and nothing here says which content types route to this one.

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?

The phrase "to the author of a public chat message, sticky, or family ping" implicitly scopes usage, which is better than nothing. But it never excludes the sibling *_tip tools or says when to prefer them, so an agent facing an ambiguous target (e.g. tipping on library or codelab content) gets no routing help.

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