Copy Subset From Standard Cost Code List

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

The description does not contradict the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false). It adds that the tool 'Creates a copy' and 'returns the newly created object (HTTP 201)', but this is consistent with the annotations. No additional behavioral traits beyond what annotations already provide.

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 (two sentences plus endpoint info) and front-loads the purpose. It includes some extra details like API endpoint, but remains well-structured and not overly verbose.

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 covers the basic purpose and required parameters. However, it omits the critical detail that the 'standard_cost_code_ids' parameter must include ancestors of the specified cost codes, which is present in the schema but not reiterated. For a tool with no output schema, the description could be more complete.

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 description coverage is 100%, so the schema already describes all parameters in detail. The description merely lists required parameters without adding new meaning. Baseline is 3.

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's action ('Copy a subset of Cost Codes from Standard Cost Code List'), the resource ('Standard Cost Code List'), and the effect ('duplicate an existing Work Breakdown Structure records as a new record'). It also distinguishes from siblings by implying it's for a subset, and mentions required parameters.

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 explicitly says 'Use this to duplicate an existing Work Breakdown Structure records as a new record,' giving clear usage context. However, it does not explicitly state when not to use it or mention specific alternatives, though the sibling 'copy_from_standard_cost_code_list' suggests an alternative for full copies.

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