Update Deleted Equipment Serial Number

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

Annotations already indicate non-destructive behavior. The description adds value by stating 'only the supplied fields are changed' (partial update) and that it 'returns the modified object on success.' No contradictions.

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 concise with 4 sentences, front-loading purpose and usage. It includes necessary details (required params, API category, endpoint) without waffle. Slightly more could be trimmed.

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 tool with no output schema and rich annotations, the description covers purpose, partial update behavior, return value, required parameters, and API context. It sufficiently equips an agent to invoke the tool correctly.

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%, so baseline is 3. The description lists required parameters (company_id, id) but adds minimal semantic information beyond the schema descriptions. The endpoint pattern helps contextualize path parameters.

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 states a specific verb ('Update') and resource ('deleted piece of Equipment'), and clearly distinguishes from sibling tools by targeting serial numbers of deleted equipment. The purpose is clear and unambiguous.

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?

The description provides context for when to use the tool ('Use this to update an existing Field Productivity records') but does not explicitly exclude alternatives or name sibling tools for non-deleted equipment. However, the focus on 'deleted' equipment guides appropriate usage.

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