yd_ads_get

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

No annotations are provided, so the description must bear the full burden of behavioral disclosure. It fails to mention return format, pagination, authorization requirements, or rate limits. The minimal phrase 'Get ads' does not sufficiently inform the agent about the tool's behavior beyond being a read operation.

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 concise and front-loaded with the verb. However, it is overly succinct and lacks structure such as examples or bullet points. Every word earns its place, but some additional context could be added without sacrificing conciseness.

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 and annotations, the description should compensate. It does not mention return format, pagination, or how the optional client_login works. The agent lacks key context to use the tool correctly, especially when compared to sibling tools that might have more detailed descriptions.

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 description coverage is only 25% (only client_login has a description). The description maps the three array parameters to the tool's purpose but does not explain how they interact (e.g., AND vs OR logic), whether parameters are optional, or the format of IDs. This leaves the agent with significant ambiguity.

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 verb 'Get' and the resource 'ads', and specifies the three filtering dimensions (campaign, ad group, ad IDs). It effectively distinguishes from sibling tools like yd_ads_add or yd_ads_update.

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 implies when to use the tool (to retrieve ads by IDs) but does not provide explicit guidance on when not to use it, alternatives, or prerequisites. For example, it doesn't mention that all parameters are optional or that the tool can retrieve multiple ads.

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