anon_post_work_modules_mid_confirm

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

The description claims '重复确认幂等，不刷新时间戳' (repeated confirmation is idempotent, does not refresh timestamp), but the annotation declares idempotentHint=false. This directly contradicts a structured behavioral hint. It does add useful context (records confirmer/time, permission requirements), but the contradiction dominates.

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 action, then behavioral notes, then parameter conditions, then the endpoint. Dense but each sentence carries information; minimal redundancy.

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 mutation tool with no output schema, it covers the endpoint, project scoping, permission model, and side effects (records time/confirmer) — but the idempotency claim is wrong, leaving the agent with an inaccurate behavioral model.

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 must carry the load. It explains userId semantics (default self, on-behalf requires elevated scopes) and clarifies that projectId is unnecessary because the project is derived from the API key, compensating well for the sparse schema descriptions and nested body/path structure.

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 (确认/confirm) and resource (成员与模块的分配关系/task assignment) plus the exact endpoint. It is clearly distinguishable from siblings like anon_post_work_modules_mid_unconfirm, _checkin, and _finish.

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 clear conditional usage: omit userId to confirm for yourself (project-member permission suffices), pass userId to confirm on behalf of another (requires work:manage or project:manage). It does not explicitly contrast with the unconfirm/checkin/finish siblings, so it stops short of full alternative routing.

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