getXTOrdersReport

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

No annotations are provided, so the description carries the burden. 'Get' implies a non-mutating read operation, but the description does not disclose access requirements, refresh behavior, or potential side effects. It adds only return-content hints beyond the schema.

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?

One sentence with the action and resource front-loaded, and no significant fluff. The minor redundancy between 'report data' and 'order information' is negligible.

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 simple two-parameter report tool with no output schema, the description gives the essential purpose and a hint of return content, but it omits useful context such as the default behavior when reportInterval is omitted and how this report differs from sibling report tools.

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 the baseline is 3. The description does not add parameter-level detail beyond the schema, though it does clarify that the report includes conversion metrics and order information.

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 uses a specific verb ('Get') and resource ('orders report data for an Experience Targeting (XT) activity'), and specifies content ('conversion metrics and order information'), making its purpose clear and distinguishable from generic report or activity tools.

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 clearly identifies the target scenario (XT activity orders report), but does not explicitly state when to prefer it over sibling tools like getABOrdersReport or getXTPerformanceReport, nor any exclusions or prerequisites.

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