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 is covered and 'Read-only' at the end is largely redundant. The description nonetheless adds real behavioral context beyond the annotations: the null/empty-state behavior when no competitor program terms have been collected, which is the only place that is documented given there is no output schema. No auth or rate-limit detail, so not a 5.

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?

Purpose is front-loaded in the first clause, and the following enumeration is dense but every item is a distinct return field rather than filler. The trailing 'Read-only' restates the readOnlyHint annotation and is the one line that does not earn its place, keeping it out of 5 territory.

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 no output schema, the description carries the full burden of describing what comes back, and it does so field by field, plus it documents the empty/null case and the precondition that competitor terms must have been discovered. Nothing an agent needs in order to call this correctly is missing.

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 exactly one parameter and schema description coverage is 100%, with the schema itself explaining 'Project id from list_apps. Omit to use your most recently added project.' The description adds no further meaning about app_id semantics or defaulting, so the baseline of 3 for high-coverage schemas applies.

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 opening clause names a specific computed resource — the project's commission offer versus competitors' published programs — which is clearly distinct from sibling readers like list_competitors (raw competitor list) or get_program (own program). It then enumerates the return contents (rates, cookie windows, market median, higher-paying open prospect sites, terms chips, affiliate directories), so an agent can identify the tool without opening a schema. It stops short of explicitly naming the sibling it should be chosen over.

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: 'benchmark null when no competitor program terms were found yet' hints that competitor data must exist first, which is a useful precondition signal. But there is no explicit when-to-use/when-not, no mention of how this differs from list_competitors or get_program, and no guidance on cadence or freshness.

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