enforce_retention

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

No annotations are present, so the description must fully disclose behavior. It only states the core action and mentions dry_run via parameter defaults, but fails to explain side effects, reversibility, or what happens to associated data. The agent is left guessing about implications.

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 sentence that efficiently conveys the core functionality. There is no redundant information, and the key action and constraint are front-loaded.

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 lack of annotations and output schema, the description provides minimal context. It omits return values, confirmation messages, or how the dry_run mode behaves. For a deletion tool, more behavioral context is needed to ensure safe usage.

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 coverage is 100%; both parameters have descriptions in the schema. The tool description adds no additional semantic value beyond summarizing the action. Thus, it meets the baseline but does not enhance understanding.

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 tool's purpose: 'Apply data retention policy by deleting sessions older than specified days.' It specifies the action (delete) and resource (sessions) with a condition (older than days). However, it does not explicitly differentiate from sibling tools like archive_conversations or clean_traces, which also handle data cleanup.

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 is provided on when to use this tool versus alternatives. Given siblings like archive_conversations, clean_traces, or wipe_traces, the agent lacks context to choose correctly. There is no mention of prerequisites, recommended scenarios, or exclusions.

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