list_completed_reminders

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

With no annotations, the description carries full burden. It discloses the key behavior (filtering by completion time, not due time) and optional parameters. However, it does not describe return format, pagination, or any limitations beyond the start advice.

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?

Reasonably concise with a clear separation of purpose and parameter details. A bit of redundancy in the examples could be trimmed, but overall efficient.

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?

Completeness is good given the simplicity: purpose, parameter semantics, and usage advice are covered. The lack of output schema is mitigated by the clear return context (completed reminders). Could mention if it returns all fields or a summary.

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?

Both parameters are explained in detail: format (YYYY-MM-DD HH:MM), optional, and concrete examples for 'past week'. This adds significant value since the schema has 0% description coverage.

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?

Clearly states it queries completed reminders with specific filtering by completion time. The description explicitly distinguishes this from listing all reminders (sibling list_reminders) by emphasizing '已完成' and '完成时间'.

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?

Provides context for when to use (reviewing/completing tasks like past week interviews) and gives practical advice to always pass a start to avoid large result sets. Does not explicitly exclude alternatives but the purpose is clear enough.

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