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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds only that the data is weekly and per-seller, without covering auth requirements, rate limits, data freshness/lag, or what the response contains — modest incremental value over the annotations.

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 front-loaded sentence carries the meaning; the trailing 'GET /retailer/insights/performance/indicator' is redundant noise for an agent that cannot call HTTP directly, but it is short and does not obscure the purpose.

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 should hint at what comes back. It says 'weekly measurements' but not the shape (score, norm, period, unit), which is the main missing piece. All three required params are fully documented, so the definition is adequate but not 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?

Schema description coverage is 100% and the 'name' enum already enumerates every indicator, so the description's indicator list is largely redundant. It does reinforce 'ISO year and week' semantics, but adds no format or edge-case detail (e.g. how weeks 52/53 behave). Baseline 3 is appropriate.

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 and resource ('weekly measurements of one bol performance indicator') and lists the eight possible indicators, plus the exact endpoint. No sibling tool covers performance indicators, so an agent can unambiguously select this one.

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 implied by the description (fetch a KPI for a given ISO year/week), but there is no explicit when-to-use guidance, no prerequisites, and no mention of alternatives or limits. The sibling list contains no comparable tool, so the gap is tolerable but real.

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