duplicate_price_list

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

With no annotations, the description does disclose two behavioral facts: an auth requirement and that the operation produces a copy (leaving the source list intact). It does not say what is returned (new list ID/URL), where the copy appears, or whether the copy inherits sharing settings — meaningful gaps for a mutation tool.

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?

Two short sentences, front-loaded with the action and followed by the auth prerequisite; nothing is wasted. The fragment "Needs a login" is terse to the point of being abrupt but costs no clarity.

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?

For a mutation tool with no annotations and no output schema, the description is too thin: an agent still cannot tell what it gets back, how to identify the new list, or what format url_or_id takes. It covers the auth and optional-name basics but leaves the critical call-shaping details unaddressed.

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 0%, so the description must carry parameter meaning. It clarifies that new_name is optional and overrides the name only, but says nothing about url_or_id — whether it accepts a URL, a numeric ID, or both — leaving the required parameter undocumented in both places.

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?

"Copy a saved price list (optionally with a new name)" gives a specific verb (copy) and resource (saved price list), which distinguishes it from rename_price_list or read_price_list by implication. It is clear but never names those siblings explicitly, so the differentiation relies on the reader inferring it.

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 prerequisite "Needs a login" is stated, which is useful context for when the call can succeed. However, there is no guidance on when to prefer duplicate over rename_price_list or read_price_list, and no explicit exclusions, so usage is only implied.

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