Update Company Inspection Template Item

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

Annotations indicate readOnlyHint=false, so the tool is a write operation. Description confirms it modifies data and returns the modified object. No contradictions. However, it does not disclose permissions, rate limits, or side effects beyond the partial update behavior.

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?

Description is three sentences, covering purpose, usage, required params, and API reference. It is concise and well-structured, though the purpose sentence could be more front-loaded. No unnecessary information.

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?

The description mentions the return of the modified object but lacks details about its structure. With no output schema, more information about the response fields would improve completeness. However, for a simple update tool, the description is adequate.

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 3. Description only lists the three required parameters without adding new meaning beyond the schema. Optional parameters (name, response_set_id, type) are not elaborated, so no extra value added.

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 (Updates) and resource (Company Inspection Template Item). It distinguishes from creation by noting it updates existing items and mentions partial update via 'only the supplied fields are changed.' Minor inconsistency: refers to 'Inspections' instead of 'Inspection Template Item,' but overall the purpose is clear.

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 states to use this tool for updating existing inspection template items with partial fields. It does not explicitly contrast with create or delete tools, though sibling tools exist. No guidance on when not to use or prerequisites beyond required parameters.

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