ym_stocks_update

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

The description says 'update', implying a mutation, which aligns with the readOnlyHint=false annotation. However, it does not disclose any behavioral traits such as authorization requirements, side effects (e.g., overwritten data), rate limits, or error behavior. The absence of annotations leaves the description solely responsible, and it falls short.

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 extremely concise, using two sentences to convey purpose and argument structure. It is front-loaded and contains no redundant information.

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 an output schema, the description need not detail return values. However, for a mutation tool with two parameters (one undocumented), the description is too minimal. It omits details like batch behavior, error handling, and prerequisites, making it insufficient for an agent to use confidently.

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?

The description explains the structure of the required 'stocks_json' parameter (JSON array with specific fields), which adds meaning beyond the raw string type in the schema. However, the optional 'campaign_id' parameter is not mentioned, and with 0% schema description coverage, the description only partially compensates.

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 updates product stocks, which is a specific verb-resource combination. However, it does not differentiate from sibling tools like ym_stocks (likely a read) or ym_prices_update, leaving ambiguity about when to use this over related 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 no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, context, or when not to use it.

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