Api privacy processings status retrieve

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the description needed to add retrieval semantics or response shape. Instead it describes a CSV/XLSX export mixin, which contradicts the read-only status-retrieve behavior implied by the name and provides zero behavioral context.

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?

It is a single short sentence, but brevity does not help when the sentence describes the wrong thing. There is no front-loaded statement of purpose, only an internal implementation note.

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 retrieve endpoint with an empty parameter schema and no output schema, the description should say what status data is returned and for which resource. It says none of that, leaving the agent with a description that describes a different capability entirely.

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 has zero parameters, so parameter semantics default to baseline 4 territory. However, the description implies export-format options (CSV/XLSX) that do not exist in the schema, which is mildly misleading even though there is nothing to document.

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 ('Generic export mixin for CSV/XLSX exports') describes an internal Python mixin, not the tool's actual behavior, which per the name and title is a status retrieval endpoint for privacy processings. It actively misdirects the agent toward an export operation that this tool does not perform.

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 guidance on when to use this tool, no mention of the sibling status-retrieve endpoints or the /privacy/processings/ family, and no conditions or exclusions. An agent has nothing to route on.

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