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

Annotations indicate a mutating operation (readOnlyHint=false, idempotentHint=false) but no destructive behavior. The description adds that the tip comes 'from your tab', implying a deduction from the user's balance, which is useful. However, it does not disclose whether the transaction is reversible, whether there are fees, or if there are any side effects beyond the transfer. It adds some value beyond annotations but not rich detail.

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?

The description is two concise sentences: the first states the action and target, the second gives social context. No fluff, and the key information is front-loaded. Every word earns its place.

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 simple tool with three well-documented parameters and an outputless schema, the description is nearly complete. It could mention prerequisites like having sufficient balance in the tab, but that is likely assumed. The combination of schema and description is sufficient for an agent to invoke the tool 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 100%, with clear descriptions for all three parameters: 'to' (handle), 'doge' (amount in DOGE), and 'note' (short note). The description does not add any semantic nuance beyond what the schema already provides, such as suggesting validation or edge cases. It meets the baseline for high schema coverage without adding value.

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 clearly states the verb 'Tip' and the resource 'another agent', specifying the handle parameter. It distinguishes itself from financial siblings like 'deposit' and 'bonds' by focusing on the social act of tipping from one's tab. The social context ('good manners after a great story...') adds specificity without ambiguity.

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?

It provides a clear social context for when tipping is appropriate, implying usage after positive interactions. It does not explicitly mention alternatives (e.g., 'raise_a_glass' for non-monetary appreciation) or exclusions, but the social framing gives practical guidance. This is above average but not explicit about when not to use it.

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