yd_metrika_upload_conversions

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only says 'Upload offline conversions' without mentioning authentication requirements, error handling, idempotency, side effects, or rate limits. This is a critical gap for an upload operation.

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 at one sentence, but it sacrifices necessary detail. While there is no unnecessary text, it is too sparse to be considered appropriately sized for a useful tool definition. It is structured adequately but lacks front-loading of key 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 that there is no output schema and the tool performs a data upload, the description should cover aspects like return values, success/failure indicators, and prerequisites. None of this is included, making the tool definition incomplete 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 input schema already provides descriptions for all three parameters (100% coverage), so the description adds no additional meaning beyond the schema. According to scoring rules, baseline is 3 when schema coverage is high and description adds no extra context.

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 states the verb 'Upload' and the resource 'offline conversions', which clearly indicates the action and distinguishes it from sibling upload tools like upload_calls or upload_expenses. However, it is very brief and does not elaborate on what constitutes an offline conversion, so it misses the top score.

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 such as yd_metrika_upload_calls or yd_metrika_conversions_status. There are no usage contexts, prerequisites, or exclusions mentioned, leaving the agent without decision support.

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