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

Beyond the readOnly/openWorld/destructive annotations, it discloses ordering ('newest first'), content type ('process metadata only, no raw product values'), empty-result behavior, and the raw-vs-label distinction. This is rich, non-redundant behavioral context.

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?

The description is long but every sentence carries signal: purpose, return shape, label semantics, empty behavior, id provenance, and optionality. The main use is front-loaded and the details are organized from most to least important.

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, it supplies the exact return shape and field semantics for the human-readable labels, which is sufficient for an agent to interpret results. Inputs are fully covered by the schema plus the added id and optionality context. No critical behavioral gap remains.

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 schema already documents ad_id, item_id, and limit; the description adds the cross-tool provenance ('same id get_ad_item_report uses') and the optional/required project_id branch. It also clarifies ad_id is the integrationId from list_ads, closing the one gap left by the schema.

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 names the exact resource ('ONE ad listing item's action-log timeline') and the diagnostic intent ('explain WHY an item ended in its current state'). It clearly differentiates from get_ad_item_report by stating it uses the same item_id and is meant to be paired with it, not confused with it.

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?

It gives the intended use case (diagnosing a failing product), source-tool relationships (item_id from list_ad_items, ad_id from list_ads), and conditional project_id routing ('call list_projects'). It does not explicitly say when not to use it or mention the analogous marketplace-history sibling, so it stops short of a full when/when-not statement.

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