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

Annotations only say readOnlyHint=true; the description adds the login prerequisite, the non-confirming nature of reads, and the 4-hour SMS resend for unconfirmed reminders — genuine side-effect context beyond the annotation. It does not describe ordering or pagination of the returned list.

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?

Five short clauses, each carrying distinct operational meaning, with the core listing behavior front-loaded. Slightly dense but no wasted sentences.

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 two-parameter read tool with no output schema, it covers login, scope, side effects, and disambiguation well. The remaining gap is explaining what activityId vs pendingOnly do and what the returned reminder records contain.

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 50%: pendingOnly is documented in the schema, but activityId has no description, and the description does not compensate — it never mentions narrowing to one activity or filtering to unconfirmed items. Baseline 3 applies since the schema carries part of the load.

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 and resource ('列出本人活动前3天和前1天的提醒及确认状态'), including the timing window that defines the record set. It is clearly distinguishable from get_my_activity_reminder (single) and acknowledge_activity_reminder (write), though it never names those siblings 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 real routing guidance: reading is not confirming, informational questions about time/place/transport/materials stay queries, and with multiple reminders the agent should ask which one. It stops short of naming the confirm tool the user would need next, but the boundary is clear.

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