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

Annotations already establish readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered; the description adds substantive context beyond that — newest-first ordering, the row payload (actor, before → after value, evaluated impact), and the visibility scoping rule. It does not mention pagination behavior beyond the schema's limit, but the ordering and content disclosure are genuinely useful.

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?

Dense and front-loaded: the resource and row contents come first, scoping and the usage directive come last. It is a single long run-on sentence with stacked parentheticals and mixed-language terms (outcome migliorato/neutro/...), which costs some readability, but virtually every clause carries information.

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 3-parameter read tool with no output schema, the description does the heavy lifting on return shape (fields per row, ordering) and on when to call it. Remaining gaps are modest: how the kpi parameter filters results, and whether results beyond the 200-row cap require narrowing.

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%, so all three parameters are already documented and the baseline is 3. The description restates outpost_id's all-visible fallback (already in the schema) and never explains that kpi acts as a filter or how it interacts with the returned rows, so it adds little meaning beyond the structured fields.

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 resource (history of operations on the seller's outposts) and enumerates exactly what those operations are: bid/budget changes, price changes, listing fixes, with actor, before → after values and measured KPI impact. The verb+resource is unambiguous and an agent can distinguish it from the sibling log_action (which writes entries) and list_clients (referenced only as a source of outpost ids).

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?

Gives an explicit situational directive: 'Use it before proposing a change to know what was already tried and how it went,' and clarifies the scoping choice (outpost_id for one outpost vs. all visible outposts). No explicit when-not guidance or named alternative for reading history at a different granularity, so it stops short of a 5.

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