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

Adds real context beyond the annotations: login is required, results are scoped to the caller's own permissions, and evidence/CDKey/redemption codes are restricted to the person themselves in the App. The read-only, idempotent nature is already covered by annotations, so this extra auth/privacy disclosure is genuine added value.

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 critical 【需要登录】 marker, but the body is a dense semicolon-chained run-on that is hard to parse and mixes purpose, parameter notes and caveats together. Compact yet at the edge of over-compression.

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 whose safety profile is fully carried by annotations and which has no output schema, the description covers auth, permission scoping, visibility restrictions and the two non-obvious params. Return-value shape is not described, but that is acceptable given no output schema is declared.

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 carries the burden and does: 'draws最近limit条' explains the limit param and 'includeFairness取完整匿名凭据' explains includeFairness. Only activityRef is left unexplained, but its meaning (an activity reference) is self-evident.

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 (查看/view) plus the resource and its facets (抽奖/奖项/入池/中奖), and the two behavioral toggles (draws limit, includeFairness). It implicitly separates itself from action siblings via '查看不等于报名或中奖确认' but never names a sibling 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?

Gives context clues – permission-scoped viewing, and the warning that viewing is not registration or winning confirmation, and that pool upload / check-in happen in the App. These imply when-not-to-use but no alternative tool is named (e.g. act_activity_raffle), so routing is left to inference.

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