fabric_update_item

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

Annotations are empty, so the description must disclose behavioral traits. It only states that this is an update operation but does not mention required permissions, irreversibility, or effects on fields not specified. For a mutation tool, this lack of transparency is insufficient.

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 description is a single sentence with no superfluous words. It is front-loaded with the verb and resource. However, it could be slightly more informative without losing conciseness.

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 simple update tool with 4 parameters and no output schema, the description is minimally adequate. It mentions the mutable fields but omits the required parameter (itemId) and does not explain optionality or behavior when fields are omitted. The tool complexity is low, so this might be acceptable, but there is room for improvement.

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?

The input schema has 4 parameters with 50% description coverage (itemId, workspace have descriptions; displayName, description lack them). The description adds some context by naming the fields that can be updated ('name/description'), but does not clarify workspace's role or provide additional syntax or semantics beyond the schema. It partially compensates for the missing schema descriptions.

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 clearly states the verb 'update' and the resource 'item', specifying the fields 'name/description'. This sufficiently conveys the tool's purpose, though it could be more specific about the full set of updatable fields (e.g., workspace is also included in the schema). It distinguishes from sibling tools like fabric_update_item_definition which update the definition, not metadata.

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?

No usage guidelines are provided. The description does not indicate when to use this tool versus alternatives like fabric_update_item_definition, nor does it mention any prerequisites or context. The agent receives no guidance on selecting this tool among the many siblings.

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