Api privacy processings agg metrics retrieve

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

Annotations declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, which is consistent with a retrieve, so there is no safety contradiction. But the description's only behavioral claim – that this is an export mixin – misrepresents the tool's behavior, so it subtracts rather than adds transparency.

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 single sentence is short and front-loaded, but its content is wrong and unrelated to the tool's actual purpose. Brevity without relevance does not earn credit; the specification is deficient, not concise.

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 zero-parameter retrieve with no output schema, the description is the only place an agent can learn what metrics or aggregation breakdown are returned. Instead it describes an unrelated export mixin, leaving the tool's contract entirely unexplained and likely to cause wrong invocation.

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 tool takes zero parameters and schema coverage is 100%, so parameter documentation is not a burden here. The description adds nothing on parameters, but nothing is needed; baseline 4 applies.

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 tool name and title identify it as retrieving aggregate metrics for privacy processings, but the description says it is a "Generic export mixin for CSV/XLSX exports" – a completely different job that belongs to the sibling export_csv_retrieve / export_xlsx_retrieve tools. An agent reading this would have no idea what data the tool actually returns, and would likely mis-select it for exports.

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?

No indication of when to use this tool versus the sibling metrics_retrieve, export_csv_retrieve, or export_xlsx_retrieve tools. Worse, the text points toward export scenarios that are handled by other tools, so the guidance is actively misleading rather than merely absent.

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