export_privilege_timeline_report

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so safety is covered. The description adds no behavioral context beyond the annotations: it does not say where the export goes, what format it takes, whether it is synchronous, or whether large day ranges are bounded.

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?

A single, front-loaded sentence with no filler. It is efficient, though its brevity contributes to the coverage gaps noted elsewhere.

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 tool with two undocumented parameters, no output schema, and many timeline siblings, the description does not supply enough to call it correctly or to route to it over alternatives. Missing are the time-window semantics, output/export format, and any differentiation from sibling timeline 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 0%, so the description carries the full burden for the two parameters. It only loosely gestures at "top" (top grants/revokes) and says nothing about the "days" window or how the two interact, leaving both parameters effectively undocumented.

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 names a concrete verb ("Gera relatório") and resource (timeline report) and specifies the report contents (top grants/revokes by identity, role, scope). However, it does not distinguish this tool from close siblings like summarize_privilege_timeline, get_identity_privilege_timeline, or list_privilege_timeline_events, leaving the agent to guess which timeline artifact it produces.

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 when-to-use guidance, no prerequisites, and no mention of alternatives despite a crowded set of timeline-related siblings. The verb "export" is the only hint that this produces a file/report rather than an inline result, and that is left implicit.

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