get_ad

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

With no annotations provided, the description must describe behavioral traits like side effects (none expected since it's a get operation), authentication requirements, or rate limits. It only states the action without any behavioral context, leaving the agent unsure about safety or data persistence.

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 a concise single sentence that front-loads the purpose. Every word contributes meaning, with no superfluous content.

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 simple tool (1 param, no output schema, no annotations), the description is acceptable but lacking completeness. An ideal description would mention the expected response structure, what 'full details' includes, or any error cases (e.g., what happens with an invalid ID).

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 schema already covers the single parameter 'id' with 100% description coverage ('The Cart ad ID.'). The description adds 'by its Cart ad ID' which mildly clarifies the source, but since schema coverage is already high, the baseline is 3—adequate but not adding transformative value.

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 retrieves details for a single ad by ID, using a specific verb ('Get') and resource ('advertisement by its Cart ad ID'). It distinguishes itself from sibling tools like search_ads and get_store_ads by focusing on a single ad and requiring a specific ID.

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 no guidance on when to use this tool versus alternatives such as search_ads or get_store_ads. It doesn't clarify prerequisites (e.g., needing a Cart ad ID from a prior search) or situations where other tools would be more appropriate.

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