Список креативов

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description adds: pagination behavior (returns page/limit/hasNextPage), apiPointBalance disclosure, and explicit list of what actions are NOT possible (modify/pause/delete). This exceeds annotation coverage meaningfully, though could mention rate limits (weekly API points).

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?

Description is a single dense paragraph, front-loaded with purpose and return structure, then filters, then constraints. Efficient but slightly long due to exhaustive field listing; no waste though.

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 read-only listing tool with 12 parameters and no output schema, description covers return fields, pagination, and constraints. Missing output schema is compensated by describing items. Could mention default pagination values, but schema already covers defaults. Overall complete enough.

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% with detailed descriptions for every parameter, including enums inline. Description reinforces filter behavior (e.g., conflict precedence for 'filter' field) but adds only marginal value beyond schema. Baseline 3 is correct.

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?

Description states 'Перечисляет креативы аккаунта' (lists account creatives) with explicit pagination and return structure. Differentiates from siblings by naming what it returns (creatives/ads) vs campaigns/groups/stats tools. Clear verb+resource.

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?

Lists all filter parameters and their semantics, implying use for filtering. Explicitly states it's read-only and what can't be done via this API. However, doesn't explicitly name sibling alternatives (like list_campaigns or creative_stats) for when to use them instead.

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