getAPTPerformanceReport

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

With no annotations, the description carries the behavioral disclosure burden. 'Get' implies a read-only report operation, and the listed data categories indicate what the report contains. However, it does not disclose any caveats such as permissions, report generation constraints, or behavior of the optional date range 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?

The description is a single, front-loaded sentence with no filler. Every phrase adds useful information: the action, the report type, the activity type, and the report contents.

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 retrieval tool with two documented parameters, the description covers the core purpose and high-level report contents. Still, the absence of an output schema and annotations means it would benefit from noting that this is a read-only operation or from pointing to sibling tools for other report types.

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%, and the descriptions for id and reportInterval already explain their purpose and format. The tool description adds no additional parameter meaning, so the baseline of 3 is appropriate.

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 the verb 'Get' and the specific resource 'performance report for an Automated Personalization Test (APT) activity'. Specifying APT distinguishes it from sibling report tools such as getABPerformanceReport and getXTPerformanceReport, and the data categories (metrics, conversions, visitor data) further clarify scope.

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?

The qualified activity type implies this tool is for APT performance reports, but it does not explicitly say when to use it instead of related report tools or when not to use it. No alternatives are named, leaving the agent to infer selection criteria from the activity type.

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