yd_metrika_upload_expenses

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

No annotations provided, so the description carries full burden. It fails to disclose behavioral traits such as whether uploads are additive or replace existing data, authentication requirements, or impact on reports.

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 short sentence with no waste, making it concise. However, it lacks structure—no explanation of context or parameters—resulting in under-specification.

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 lack of output schema, no behavioral disclosure, and incomplete object schema for expenses, the description is grossly incomplete. The agent cannot properly invoke the tool without additional knowledge of the expense format.

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 coverage is 100% for top-level parameters, but the expenses parameter's items are only typed as 'object' with no property definitions. The description adds no meaning beyond the schema, leaving the agent uninformed about the required expense structure.

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 'Upload advertising expenses,' which specifies the action (upload) and resource (advertising expenses). It is distinguishable from sibling tools like upload_calls and upload_conversions.

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 on when to use this tool versus alternatives. The description does not mention prerequisites, workflow context, or whether to use over other upload tools.

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