Update Standard Cost Code List

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

Annotations already declare not readonly, not destructive, not idempotent, and open world. The description adds that it returns the modified object on success and performs a partial update (only supplied fields changed). No additional behavioral traits like permissions or failure handling are 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?

The description is concise with 4 sentences, front-loading the purpose. It includes optional API reference information that may be extraneous but does not detract. Could be slightly more streamlined.

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 nested object parameter with additionalProperties, the description does not specify which fields can be updated within 'standard_cost_code_list'. No output schema is provided, but return behavior is noted. The description is adequate but leaves significant gaps about the update fields.

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 schema already documents all parameters. The description merely repeats the required parameter names without adding semantics about the values expected in 'standard_cost_code_list'. Minimal value beyond schema.

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 'Update' and the resource 'Standard Cost Code List' at 'Company level'. It distinguishes from siblings by specifying the scope and the type of update, but does not explicitly differentiate from other update tools.

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 some usage guidance: 'use this to update an existing Work Breakdown Structure records (only the supplied fields are changed)' and lists required parameters. However, it fails to mention when to use alternatives like create_standard_cost_code_list or sync_standard_cost_codes.

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