anon_post_work_modules_mid_finish

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

The description explicitly states 『重复完成幂等，不刷新时间戳』 (repeated completion is idempotent, the timestamp is not refreshed), while annotations declare idempotentHint=false. This is a direct, material contradiction about the operation's repeat behavior, which is exactly the trait an agent relies on to decide whether re-calling is safe.

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 action and its side effects are front-loaded, followed by the endpoint and the auth note. Every sentence adds information (completion, check-in, idempotency, auth), though packing four traits into one run-on sentence hurts scannability slightly.

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 nested-body POST mutation with no output schema, the description covers the side effects, the source of project scoping, and the body/permission source. It is close to complete, but the body parameter is only defined by reference and the (erroneous) idempotency claim undercuts what an agent needs for safe retries.

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 0%, so the description must carry the burden. It usefully clarifies that projectId is derived from the API key and that the body matches confirm, but it never explains the userId body field (target member / defaults to self) and defers the body definition to another tool, leaving a real gap.

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?

The description opens with a specific verb+resource (『标记任务完成』 = mark the task finished) and names the concrete side effects it records (completedAt, supplementary check-in for un-checked-in members). It is clearly distinguishable from its siblings confirm/checkin/unconfirm, and it points to confirm as the reference for body/permissions.

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?

It gives implied usage context (idempotent repeat calls, request body/permissions same as confirm) but never states when to prefer this tool over confirm, checkin, or unconfirm, nor when-not to call it. The cross-reference to confirm is helpful but the when-to-use decision 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.