Автозагрузка: инфо об объявлениях

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

Annotations already provide readOnlyHint=true and idempotentHint=true. Description adds no additional behavioral details beyond confirming it returns information. No contradiction, but also no extra context like rate limits or auth requirements.

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 concise (two short phrases) and front-loaded with purpose. It could be slightly more structured but remains efficient and easy to parse.

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 one required parameter with clear schema and annotations covering safety/idempotency, the description is adequate for basic usage. However, no output schema and no mention of return format or limits on ID count leave some gaps.

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?

Only one parameter 'query' with 100% schema coverage. Description restates what schema says (CSV list of IDs), adding no new semantic value beyond schema description. Baseline 3 applies as schema already covers parameter meaning.

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 clearly states it provides information about ads in autoload by ID, with the query parameter specified as CSV list of IDs. This distinguishes it from siblings like autoload_get_profile or autoload_get_reports.

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?

Description explains what the tool does but does not provide when to use it versus alternatives, nor any exclusions or prerequisites. Absence of usage guidance limits its utility for agent decision-making.

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