update_asset

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

Annotations already indicate a readOnlyHint=false, destructiveHint=false, and idempotentHint=true. The description adds only '[Write]', which is already implied. No additional behavioral context (e.g., permissions, side effects, or what happens on update) is disclosed.

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?

Very concise: one sentence plus a tag. However, it lacks any structure (e.g., bullet points) that could enhance readability.

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 parameter (fields) and no output schema, the description is insufficient. It does not explain how to structure the fields object or what the tool returns, leaving agents with ambiguity.

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 100% with descriptions for both parameters. The description adds no extra meaning beyond what the schema provides, so baseline 3 is appropriate.

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?

Description states 'Update an IT asset record' with a clear verb and resource. It distinguishes from siblings like create_asset and retire_asset, but does not explicitly differentiate from update_record.

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 guidance on when to use this tool versus alternatives (e.g., update_record, retire_asset). No prerequisites or scenarios provided.

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