ad_manager_li_get_reporting_list

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

Annotations already convey readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe, non-mutating operation. However, the description adds no behavioral context beyond those flags – it does not mention what the returned list contains, whether pagination is involved, or any special constraints (e.g., date range limits). With annotations covering the safety profile, a 2 reflects the lack of any additional behavioral detail.

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 extremely short, but this is under-specification rather than conciseness. It conveys only a vague intent and does not front-load any useful constraints or clarifications. While there is no wasted text, the structure fails to provide the agent with decision-relevant information. A concise description should still be informative; this one is just terse.

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 the tool has 7 parameters, 5 required, and no output schema, the description must clarify what the tool returns and how to interpret the parameters. It does neither. The description is insufficient for an agent to know what a 'reporting list' is or how to differentiate it from other reporting endpoints. The presence of sibling tools that are similarly named makes the lack of context especially problematic.

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 every parameter has a description (e.g., 'Start date in yyyy-mm-dd format', 'Campaign ID'). The tool description itself adds no parameter guidance – it does not explain how parameters relate to each other or what 'fields' list implies. Since the schema already documents the parameters well, the description does not need to repeat that, and a baseline 3 is appropriate. It could improve by clarifying the 'listType' parameter, which is simply 'List type' and offers no examples.

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 'Get reporting list' states a verb and a noun, but 'reporting list' is ambiguous – it does not specify what kind of list (e.g., list of reports, list of metrics, list of campaigns) or for which ad platform (LinkedIn is implied by the name but not in the description). It does not distinguish this tool from siblings like ad_manager_li_get_campaign_group_reporting or ad_manager_li_get_ad_analytics, which also deal with reporting. The resource is too vague to be actionable.

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?

There is no guidance on when to use this tool versus its many siblings. No mention of context, prerequisites, or conditions that would make this tool the right choice. For example, it does not say 'Use this for a list of report entries, while ad_manager_li_get_campaign_group_reporting returns aggregate campaign stats.' The absence of any usage guidance is a critical gap given the large number of similar ad_manager tools.

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