kadam_adv_get_extended_stats

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

Annotations declare readOnlyHint=true, and the description confirms it's a stats grid, consistent with read-only. It adds behavioral details beyond annotations: the need for Bid Optimization access and the pattern of re-using pathIds for bid updates. No contradictions.

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?

Three sentences with no wasted words. The first sentence states purpose and requirement, the second explains the drill/reuse pattern, and the third gives a cardinality tip. Information is front-loaded.

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?

Given 11 parameters, low schema coverage, and no output schema, the description covers the core functionality and essential parameters well. It lacks detail on date range, search, and pagination but provides enough context for an agent to select and invoke the tool correctly.

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 low (36%), but the description adds significant meaning to key parameters: it explains how pathIds work (drill path, slice IDs), enumerates valid metric and sortField keys, and clarifies that campaignIds should be a single campaign for per-row bids. This compensates for the coverage gap.

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 clearly states 'Bid Optimization: per-slice stats grid for drilling down and setting bids,' which is a specific verb+resource combination. It distinguishes from sibling tools like kadam_adv_get_stats (general stats) and kadam_adv_list_extended_bids (list bids) by focusing on drill-down and bid-setting context.

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?

Explicitly states requirement ('requires Bid Optimization access'), provides when-to-use guidance ('Drill by appending a sliceId to pathIds'), and instructs how to re-use results ('reuse each row's pathIds to set bids via kadam_adv_update_extended_bids'). It also advises cardinality ('Use ONE campaign to see per-row bids').

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