tcg_watchlist_update

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

Annotations provide minimal hints (readOnlyHint=false, destructiveHint=false, etc.), so the description should clarify behavior. It only says 'update mutable fields', omitting whether partial updates merge, whether nulls clear fields, or what happens to omitted fields. This is insufficient for mutation behavior.

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 a single sentence, which is concise but under-specified. It lacks structure (e.g., bullet points for parameters). While brief, it could be expanded without losing conciseness.

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 tool has 1 parameter (a nested object with 6 sub-fields), complex update semantics, and an output schema (not shown), the description should explain behavior like merge vs replace, return value, and possible errors. The current description leaves significant gaps.

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%, meaning no parameter descriptions exist. The tool description does not elaborate on any parameter (e.g., meaning of horizon enum, target_price format). The description adds zero value beyond parameter names, failing to compensate for the schema gap.

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 'watchlist entry', with 'mutable fields' adding specificity. It clearly distinguishes from sibling tools like tcg_watchlist_add (create) and tcg_watchlist_get (read).

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 is given on when to use this tool versus alternatives (e.g., tcg_watchlist_close or tcg_watchlist_add). The description lacks context about prerequisites or typical use cases.

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