Raw Avito Ads API call

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

Descriptions adds significant behavioral context beyond annotations: path validation (replaces {accountID}, refuses other accounts, blocks escaping base), body sent as JSON, no client-side validation, irreversibility, confirmWrite semantics, and return value (raw response + apiPointBalance). This is rich and non-contradictory with the annotations.

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 dense but every sentence carries essential information: purpose, examples, validation rules, safety warnings, and comparisons to alternatives. It is front-loaded with purpose and structured logically, with no filler.

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 dangerous raw API tool with no output schema, the description covers invocation details, safety, path constraints, method behavior, and return value. It is complete enough for an agent to use safely and correctly, including edge cases like POST for reads.

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?

Even though schema coverage is 100%, the description adds crucial meaning: explains how path placeholders are replaced, account-scoping rules, that body is JSON, and the meaning of confirmWrite. This goes well beyond the schema field descriptions and helps correct invocation.

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's function: an escape hatch to call any Avito Ads API path directly for endpoints without a dedicated tool. It uses specific verbs and resource scope ('call any Avito Ads API path') and differentiates from siblings by explicitly noting it covers endpoints without dedicated 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 explicit when-to-use guidance (endpoints without a dedicated tool) and names alternatives: 'prefer transfer_funds / delete_user / create_* when they exist'. It also explains when confirmWrite is required and that GET is safe, giving clear usage context.

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