cleanup_tuning_sessions

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

The description discloses the destructive action ('delete') and the default protection of active sessions. However, it does not detail whether deletion is permanent, if there are side effects, or required permissions. With no annotations, the description carries the burden but provides only minimal 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?

A single, well-structured sentence that conveys the core action and a key detail (default protection). No unnecessary words, making it easy to parse quickly.

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 simple two-parameter cleanup tool, the description covers the primary purpose and default behavior. However, it omits details about the return value (output schema exists but not explained) and potential failure cases. The description is adequate but not thorough, especially given no annotation support.

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 has two parameters (keep_last, include_active) with defaults but no descriptions. The schema coverage is 0%, and the description does not explain their meaning or usage beyond a hint about protecting active sessions. This leaves the agent to infer semantics from parameter names and defaults, which is insufficient.

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 deletes older tuning sessions and protects active ones by default. It uses specific verb 'delete' and resource 'tuning sessions', distinguishing it from siblings like archive_tuning_session.

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 explicit guidance on when to use this tool versus alternatives. The description only implies it's for cleanup, but does not mention when not to use it or list sibling tools like archive_tuning_session as alternatives.

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