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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds the important context that the endpoint is public with no auth required, which is behavioral info not present in the annotations. It also explains the data bundle's purpose without contradicting the annotations.

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 two sentences: the first defines the resource and its contents, the second gives usage context and auth status. Every sentence adds value with no redundancy or filler.

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 simple single-parameter GET with a rich annotation set and clear sibling context, the description fully covers the tool's purpose, usage timing, and access requirements. The lack of an output schema is acceptable given the straightforward nature of fetching a manifest.

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?

There is only one parameter (`slug`) and schema description coverage is 100%, with a clear example provided. The description reinforces that the slug is part of the URL path but adds no new semantics beyond the schema, warranting the baseline score for high coverage.

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 wraps the public `/embed/<slug>/manifest.json` endpoint, identifying the specific resource (per-embedder manifest) and the verb (get). It also lists the manifest's contents (creative formats, voice options, payout config, beacon URLs), distinguishing it from the network-level sibling `get_embedder_network_manifest`.

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 explicitly says to use it after `register_embedder` or when reading another partner's manifest to plan an ad buy. This provides clear usage context, though it doesn't mention when not to use it or name alternatives such as `get_embedder_network_manifest`.

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