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

Annotations already declare readOnlyHint=true, and the description reinforces this by explicitly denying check-in writes and auto-registration/ticketing ('不会执行签到写入', '不自动报名或购票'). It additionally discloses a login requirement and the human-in-App verification flow (geolocation or on-site dynamic code), which annotations do not convey. Return format is not described, keeping it at 4.

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 login requirement is front-loaded and the sentences are dense but purposeful. There is minor redundancy between '只读' and '不会执行签到写入', but the extra emphasis is defensible given the misleading tool name.

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 read-only tool with no output schema, the behavioral picture (login, read-only, no auto-registration, App-only verification) is fairly complete. However, the 4-parameter surface with 25% coverage, particularly the legacy 'preview'/'previewHash' parameters, is left unexplained, leaving the agent guessing about non-required inputs.

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 25% — only 'consent' is documented, while 'preview' and 'previewHash' have no schema text. The description does not explain any parameter, offering only the vague hint '保留旧参数兼容'. At low coverage the description is expected to compensate, and it largely does not.

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?

Despite a misleading name ('check_in') that implies a write, the description explicitly redefines the tool as a read-only status check plus an App resume entry ('只读本人活动签到状态和 App 续接入口'). This is a specific verb+resource distinction an agent can act on. It does not name a sibling tool, so it stays at 4 rather than 5.

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 description states clearly when this tool applies (reading own check-in status) and when it does not (Agent/web/mini-program never perform on-site check-in; the user must do it in the App after completing their profile). The only gap is that it does not point to a specific alternative sibling such as check_activity_eligibility or get_activity_attendance.

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