Update Classification

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

Description discloses that only supplied fields are changed (PATCH semantics) and returns the modified object. Annotations only provide basic hints, so this adds meaningful behavioral context beyond annotations.

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 mixes usage instruction, required parameters, and API reference in a somewhat unstructured way. It is fairly concise but includes redundant repetition of title and could be better organized.

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?

Description covers the basic operation (input, partial update, return value) but lacks details on error scenarios, permissions, or behavior when no fields are supplied. Adequate for a simple update tool but not fully comprehensive.

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. Description repeats required parameters and mentions URL vs body fields, but these are already covered by schema descriptions. No new semantic information 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 it updates an existing classification (Company Settings) and that only supplied fields are changed. Verb and resource are specific: 'Update Classification' and 'update an existing Company Settings'.

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 like 'create_a_new_classification' or the sibling 'update_a_classification'. No exclusions or prerequisites provided.

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