Update Equipment Category (Company)

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

The description discloses it performs a partial update (PATCH), only modifies supplied fields, and returns the modified object. It goes beyond annotations which only provide read/destructive hints. No contradiction with annotations; the description adds operational detail.

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 four sentences, front-loading the purpose. It includes optional details like API version and endpoint, which may aid debugging but do not pad unnecessarily. Slightly verbose due to endpoint info, but still efficient.

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?

Given the moderate complexity (4 params, no output schema), the description adequately states the operation, required parameters, and return behavior. It lacks error handling details but covers essential context. The tool's company-level scope is clear.

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 the input schema already documents all four parameters with descriptions. The description merely restates the two required parameters. No additional semantic value is added beyond what the schema provides, meeting the baseline for high coverage.

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 tool updates an equipment category at the company level. It specifies that only supplied fields are changed and returns the modified object. The title and description align, and it is distinct from sibling tools like create_equipment_category_company.

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 does not provide guidance on when to use this tool versus alternatives. It lacks information on prerequisites, when not to use, or comparisons to similar update tools. The agent would need to infer usage context from the tool name alone.

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