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

No annotations are provided, so the description must carry the behavioral burden. 'Get' clearly implies a read operation, and the description is transparent about what the returned record contains. It does not discuss not-found behavior or auth requirements, but for a simple slug-based getter this is a minor gap.

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?

A single, well-structured sentence that front-loads the action and resource, then packs the key record fields into a parenthetical. Every element adds useful information with no repetition 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?

With one required parameter, no annotations, and no output schema, the description covers the essential context: the lookup key and the content of the returned record. It could mention what happens if the slug does not exist, but the tool is simple enough that the description is otherwise complete.

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 provides only 'slug' with type string and no description, so the description's 'by its slug' adds the essential meaning: the slug is the unique locator for the affiliate program. It does not give format examples or constraints, but for a single identifier parameter this is sufficient.

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 ('Get') and a clear resource ('full verified record for one affiliate program'), identified by slug. It also enumerates the record's contents, distinguishing it from broader search or list 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?

The description establishes clear context: use this tool when you already have a specific affiliate program slug and need the full record. It does not explicitly name alternatives like search_affiliate_programs or state when not to use them, but the singular-by-slug framing makes the intended use obvious.

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