List ad groups

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the description's value is limited. It adds the behavioral note about the API requirement for selection criteria, but no other traits are disclosed.

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 two sentences long, front-loading the purpose ('Lists ad groups') and then adding the key constraint. Every sentence is informative with zero waste.

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 annotations (readOnly, idempotent, etc.) and complete schema descriptions, the description covers the critical usage requirement. It does not explain pagination behavior, but autoPaginate parameter is documented in schema. Overall sufficient for a list operation.

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 parameter schema has 100% coverage with individual descriptions. The tool description adds cross-parameter meaning by stating that at least one of campaignIds or ids is required, which is not clear from individual param descriptions alone.

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 'Lists ad groups' as the verb+resource, and adds a specific constraint about required selection criteria. It distinguishes this tool from siblings like list_ads or list_campaigns by focusing on ad groups.

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 explicitly says 'Provide campaignIds and/or ids — the Yandex Direct API requires at least one selection criterion.' This gives a clear usage condition, though it does not mention when not to use or name alternatives.

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