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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the safety profile is largely covered. The description nonetheless adds genuine value: it warns that customer data is not instructions (prompt-injection hygiene) and clarifies that no browser is supplied and nothing is submitted externally. It omits what happens if opportunity_id is unknown or when materials are missing, so it falls just short of full transparency.

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 three compact sentences with the resource enumeration front-loaded directly after the verb. Each sentence contributes something distinct: contents, safety posture, and external-effect boundary. The long comma list is dense but purposeful rather than redundant.

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?

An output schema exists, so return structure need not be explained, and the description correctly focuses on scope and boundaries. For a single-parameter read tool with full annotation coverage, the remaining gap is the relationship to the near-identical get_directory_handoff sibling. Error behavior for an invalid opportunity_id is also unstated.

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 a single required parameter with 100% schema description coverage, so the schema already defines opportunity_id as the curated backlink opportunity identifier. The description adds no syntax, format, or validity detail beyond that. Baseline 3 is appropriate when the schema carries the parameter semantics.

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 uses a specific verb ('retrieve') and enumerates the exact payload: approved descriptions, public business details, destination rules, missing materials, tracker version. This clearly distinguishes the resource from siblings such as get_backlink_draft or get_backlink_attempt. However, it never names or contrasts the closest sibling (get_directory_handoff), leaving an agent to infer the difference between two handoff-preparing tools.

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?

Usage is only implied: an agent must infer that it should supply an opportunity_id to fetch a pre-submission package. There is no explicit when-to-use statement, no sequencing guidance (e.g., call after list_backlink_opportunities, before submission), and no exclusion versus get_directory_handoff. The negative scoping ('submits nothing externally') helps set boundaries but is not usage guidance.

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