anon_post_work_modules_mid_checkin

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

The description asserts '重复签到幂等' (repeat check-ins are idempotent and do not refresh the timestamp), which directly contradicts the annotation idempotentHint=false. It also says nothing about the destructiveHint=true annotation, leaving the agent with conflicting safety signals.

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-loads the action and its key behavioral note (idempotency, checkedInAt), then permissions, then the endpoint. Dense but every clause carries information; no filler.

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 2-param, nested-body POST with no output schema, the description covers permissions, defaulting, and the side effect. However it omits any description of the response and provides no explanation of the destructive behavior the annotations advertise, and its idempotency claim conflicts with them.

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?

Only 2 parameters with 0% schema description coverage, so the description must carry the load: it explains that body.userId defaults to self and that mid is the work-module id in the path, and that projectId is not needed. Semantics of both parameters are effectively covered.

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+resource (任务签到 / work-module check-in) and records the concrete side effect (checkedInAt), plus the endpoint. It also names the confirm sibling it parallels. The 'same body/permissions as confirm' phrasing blurs the boundary slightly, but an agent can still tell check-in apart from confirm/unconfirm.

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 concrete invocation context: omitting userId means self check-in, project members are sufficient, and projectId is derived from the API key. It does not explicitly say when to prefer this over confirm/unconfirm, but the permission and defaulting guidance removes most ambiguity.

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