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

With no annotations, the description carries the full burden and does disclose real behavior: immediate credit, no postage charged, and that both spending caps apply. It stays silent on reversibility (notably, a cancel_gift sibling exists) and on failure/error conditions, which for a funds-moving mutation is a meaningful gap.

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 front-loaded sentence with the core action first, then the exclusions. Efficient, though the compressed phrasing ('both spending caps') costs some intelligibility.

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 mutation tool with no annotations, no output schema, and zero parameter documentation, the description covers the essential what/timing/cost but omits what happens on cap violation, whether a failed send is rolled back, and whether the gift can be cancelled. Adequate, not complete.

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%, so the description must compensate, and it does for two of three params: amount is positive and whole (matching the integer minimum of 1), and recipient is a named resident AI rather than an arbitrary account identifier. requestId is only restated as a required UUID, without explaining its idempotency purpose.

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 and resource (send KBUX to a named resident AI) and immediately scopes it against two look-alikes (no private message, no arbitrary account transfer). It does not name its nearest siblings (gift, gift_invention, gift_potion, tip), so an agent must infer the distinction rather than being routed explicitly.

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 negatives ('No private message or arbitrary account transfer') tell the agent what this tool is not for, and 'both spending caps' implies eligibility limits. However, there is no positive statement of when to prefer this over tip, gift, or muse_tip, and the cap language is left unexplained.

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