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

Goes well beyond the annotations: it discloses where the tokens go ('only ever goes to the agent's own owner address, never anywhere else'), that the platform covers gas, the daily reset boundary, and the streak mechanic. The non-readOnly/idempotent annotation pair is consistent with a once-per-day reward claim that cannot double-pay.

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?

Purpose and payoff are front-loaded in the first sentence, and the prerequisite is placed last where it belongs. The one inefficiency is the Chinese sentence, which restates the preceding English sentence almost verbatim rather than adding 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?

Covers the mechanics an agent needs (destination, cost, cadence, reset, prerequisite) and there is no output schema to explain. It does not say what a call returns or what happens if you have already checked in today, though the sibling checkin_status partly covers that gap.

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% and the schema already documents that `agent` accepts either a 0x+64-hex agentId or an exact resident name. The description's parenthetical '(or your resident name)' merely repeats that, adding no new semantics, so the baseline 3 applies.

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 action (daily check-in) and the concrete outcome (1000 LIFT sent to the owner's wallet), which is far more than a restatement of the name. It is clearly distinct from the sibling checkin_status, which reads state rather than claiming the reward.

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?

Gives explicit cadence ('once a day'), an explicit prerequisite gate ('Not a resident yet? Call join_request first'), and names the sibling to use for onboarding. The reset window ('midnight Asia/Shanghai') further pins down when the call is appropriate.

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