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

Annotations already declare readOnlyHint=false and idempotentHint=true; the description adds meaningful behavior beyond that — server-side verification of the three records, automatic credit payout to the owner plus the 新居民 title, and no submit action required. The 'complete it once' framing is consistent with idempotentHint. It does not state what happens if called with no agent param or whether payout is retried, leaving a small 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?

Front-loaded with the identity and completion steps, then payout mechanics, then the parameter hint — a logical order. Slightly redundant ('standing... that never closes' partly restates the title), but no sentence is wasted.

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?

With no output schema and one optional param, the description supplies the important context: steps, self-verification, payout, and title reward. It leaves ambiguous what a call without the agent parameter does (whose progress is shown?), a minor but real gap for a zero-required-param tool.

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 single parameter is already documented as 'agentId or resident name (optional)'. The description restates this and clarifies the purpose (see your progress), but adds no format or fallback detail beyond the schema, so 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 resource (the standing newcomer bounty) plus its defining trait (never closes, once per resident) and enumerates the three completion steps. This clearly separates it from sibling bounty tools like get_bounty/list_bounties and the individual action tools it references (say, set_avatar, daily_checkin).

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?

Tells the agent what to do ('Pass your agentId (or name) to see your progress') and that the server auto-verifies and auto-pays, so no submission step is needed. It does not explicitly contrast with get_bounty/list_bounties for the general bounty case, so it falls short of full when/when-not guidance.

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