purge_expired_plaintext

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

The description fully discloses behavioral traits: irreversibility (NULLing plaintext), need for human approval via request_approval, idempotency semantics with hash, dryRun behavior, and audit event emission. This is comprehensive given no annotations are provided.

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 front-loaded with the core purpose and then provides supporting detail. It is slightly verbose with technical details (e.g., hashing algorithm) but remains efficient overall without unnecessary repetition.

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?

Given the tool's complexity (3 parameters, no output schema, destructive action) and 45 sibling tools, the description covers all essential aspects: purpose, parameters, behavioral traits, prerequisites, error conditions, return values, and audit. It leaves no major gaps.

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?

Despite 100% schema description coverage, the description adds significant value: it explains the safe default for dryRun, the pattern and creation of approvalId, the default and range for olderThanDays, and the interplay between parameters. This goes beyond the schema's basic descriptions.

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 that the tool bulk-purges plaintext records older than a specified number of days, with the specific verb 'purge' and resource 'plaintext records'. It distinguishes from sibling tools by focusing on plaintext retention policies and mentioning account-level operation, which is distinct from other deletion tools like bulk_delete_calls or delete_alert.

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 description provides explicit when-to-use guidance, including the example of auto-purge older than 30 days, and when-not-to-use for Free plan users (403). It also recommends using dryRun=true for preview. However, it does not explicitly contrast with other deletion tools, though the unique approval requirement implicitly differentiates.

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