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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds one piece of real behavioral information beyond that - that include_images may attach sampled video frames, implying a heavier media payload - but says nothing about response size, latency, or access permissions on the workspace.

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?

Two short sentences, zero filler, with the core purpose front-loaded and the one non-obvious parameter behavior appended second. Nothing is repeated from the title or annotations.

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?

The description sketches the return contents (details, links, findings), which partly compensates for the absent output schema, and the safety profile comes from annotations. What is missing for a 3-parameter tool is any grounding of the two required identifiers, which is the main gap an agent would hit when calling it.

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 0%, so the description carries the full burden, and it only explains include_images. The two required parameters ('ad' UUID and 'workspace') are left completely undefined in both schema and description, so an agent must guess what workspace identifies and where the ad id comes from.

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?

States a specific verb (read) and enumerates the resource contents it returns: ad details, links, and saved findings. That distinguishes it from the sibling competitor_ads_list (which lists) and competitor_ad_reference_save (which writes), though the description never names those siblings to make the contrast explicit.

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 wording 'Read ad details' implies a single-ad fetch, so an agent can infer it is the detail counterpart to competitor_ads_list, but there is no explicit when-to-use, no prerequisite (e.g., needing an ad UUID from a prior list call), and no stated exclusions.

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