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

With no annotations, the description carries the full burden. It usefully discloses that this returns aggregate headline numbers rather than detailed records, and even specifies a verification-count metric. It does not mention whether the data is cached, live, or limited in any way, but for a simple stats read the transparency is adequate.

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, immediately readable sentence. The phrase 'Headline coverage' front-loads the aggregate nature, and the rest of the sentence lists the exact metrics. No filler or repetition.

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 zero-parameter tool with no output schema and no annotations, the description tells an agent what it will learn: total programs, categories, networks, and verified-against-source count. It could add the return shape, but the core information needed to select and invoke the tool correctly is present.

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 tool has zero parameters and 100% schema description coverage, so the baseline is 4. The description does not need to explain parameters; it instead clarifies what the resulting statistics cover, which is the only relevant semantic information.

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 identifies the resource (directory) and states that it provides headline coverage: total programs, categories, networks, and verified counts. It does not use an explicit verb like 'returns' or 'lists,' but the meaning is clear and distinguishes it from sibling tools that fetch individual programs or list categories/networks.

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?

There is no guidance about when to choose this tool over siblings such as get_affiliate_program, list_categories, list_networks, or search_affiliate_programs. The aggregate nature of the stats is implied, but no explicit when-to-use or when-not-to-use instruction is given.

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