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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and idempotency are covered by structured data. The description's real contribution is enumerating what the record contains, which is valuable given there is no output schema, but it says nothing about behavior on an invalid or missing id, nor whether the postback URL template or IP whitelist are returned verbatim.

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 compact sentence with the noun phrase front-loaded and no redundant restatement of the title. It is a fragment rather than a full clause, which is marginally telegraphic, but every listed item is informative given the absent output schema.

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 one-parameter read tool with rich annotations in place of an output schema, the description covers the essential gap by listing the fields returned. What it lacks is error/not-found behavior and any pointer to the sibling list tool for obtaining the id, which keeps it short of fully 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?

There is a single parameter (id) with 100% schema description coverage, so the schema already carries its meaning. The description adds no format, range, or provenance detail for the id (e.g. whether it comes from list_aff_networks), which is the expected baseline for a one-parameter tool with full schema 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?

"One affiliate network:" states a specific resource and singular scope, and the enumerated fields (click-id parameter, postback URL template, IP whitelist, tags) make clear this is a full single-record fetch rather than a listing. It does not explicitly name list_aff_networks or get_offer as the contrasting siblings, so differentiation is implied rather than stated.

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 word "One" hints that this retrieves a single record where list_aff_networks returns many, but there is no explicit when-to-use statement, no mention of the list/update/create siblings, and no stated prerequisite such as needing an id obtained from list_aff_networks. An agent must infer the routing from the tool name alone.

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