set_time_travel_retention

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

With no annotations, the description fully discloses behavior: it runs ALTER DATABASE, returns effective settings, and notes potential no-op on SQL Analytics Endpoint.

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 concise, with a summary line, SQL example, usage note, and arg list. Every sentence is informative and well-structured.

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?

The tool is straightforward; the description covers all necessary context: purpose, parameters, behavior, return value (output schema exists), and edge cases.

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?

Parameter descriptions explain workspace, item, and days (with valid range 1-120). This adds value beyond the input schema, which only provides titles and basic constraints.

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 it sets time-travel retention period on a warehouse, and even shows the SQL command. It is distinct from sibling tools like set_audit_retention or set_result_set_caching.

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?

It notes that this is primarily a Data Warehouse concept and running on SQL Analytics Endpoint may be a no-op, providing context on when to use. However, it does not explicitly compare with alternatives or say when not to use.

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