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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is fully covered. The description's useful addition is the returned field set (id, name, offer count) in the absence of an output schema. It says nothing about ordering, total counts, or pagination behavior beyond what the schema states.

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 short sentence that front-loads the verb and resource and appends the payload fields in parentheses — nothing redundant. It is arguably over-terse rather than padded, so it errs on the right side.

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?

A simple, non-destructive list tool with zero required params, full schema coverage, rich annotations and no output schema; the description plugging in the returned fields closes most of the remaining gap. Only ordering and pagination semantics are left unstated, which is minor here.

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 100%, and the three parameters (page, search, per_page) carry their own defaults and bounds, so baseline 3 applies. The description adds nothing about parameter behavior — e.g. whether 'search' is substring or prefix matching — that the schema does not already provide.

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-resource pair ('List affiliate networks') and even names the fields returned (id, name, offer count), which the title alone does not. It does not explicitly distinguish itself from get_aff_network, but the 'list' prefix against a get/create/update family makes the intent recoverable.

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?

No when-to-use guidance at all: nothing says to use this for discovery/pagination versus get_aff_network for a single network, and no mention of how 'search' interacts with paging. The agent must infer usage from the name and sibling naming convention.

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