harvest_get_ad

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

No annotations are provided, so the description carries the full burden. It discloses that the tool is a read operation ('Get') and adds a constraint about parameters. However, it does not mention return format, error behavior, or authentication needs. For a simple retrieval tool, this is adequate but leaves clear gaps.

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 single sentence that is front-loaded with the action and resource, then adds the critical parameter requirement. Every word earns its place; no unnecessary detail.

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 straightforward get tool with two optional parameters and no output schema, the description covers the essential context. It states the core function and the key constraint. It lacks explicit return-value details, but that is often implicit for a 'Get' tool. Overall, it is complete enough for a simple tool.

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 fully describes both parameters (100% coverage). The description adds meaningful relational semantics by clarifying that at least one of adId or url is required, which is not evident from the schema (no required fields). This goes beyond mere parameter definitions.

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 'Get LinkedIn Ad by ID' — a specific verb and resource. It distinguishes from sibling harvest_search_ads by indicating it fetches a single ad by identifier or URL, rather than searching.

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?

It provides a prerequisite ('requires at least one of adId or url') which tells users when the tool can be invoked, but it does not explicitly compare to alternatives like harvest_search_ads. Usage context is implied by the name and parameter requirement, but no exclusions are stated.

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