anon_patch_physical_items_item_id

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

Annotations already declare non-readonly, destructive, non-idempotent, open-world behavior, so the bar is lower. The description adds the auth scope (materials:manage) and the responsibleId clearing rule, but does not explain what 'destructive' means here or whether omitted fields are left untouched. No contradiction with annotations.

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 purpose, then permission, then field semantics, then the raw endpoint and the auto-injected project — no filler. Dense but every clause contributes; only minor gain from splitting the endpoint line out.

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 a nested body and no output schema, it covers the essentials: permission requirement, optional-field semantics, the null-clearing rule, and the fact that projectId is auto-derived so the agent won't pass it. Missing only a note on update/clear behavior for other fields.

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 effectively 0% per the context signal, so the description should carry more weight. It conveys two important semantics (all body fields optional, responsibleId null/empty clears the owner) and explains the injected projectId, but leaves the remaining body fields (name, note, spec, tags, unit, status, quantities) to the schema names alone.

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 (更新物资条目) and names the actual endpoint (PATCH .../physical/items/{itemId}), so it is clearly a partial-update tool. It implicitly separates from the create (post) and delete siblings via '字段同新建' and the PATCH verb, but does not call out those siblings by name.

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 a real precondition (需 materials:manage 权限) and clarifies the update is a partial one with all fields optional, which is useful usage context. However there is no explicit when-to-use vs alternatives guidance (e.g. when to use this versus post_physical_items or the log endpoint).

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