list_deleted_bots

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

With no annotations, the description carries full burden. It identifies the operation (read) and scope (soft-deleted, user-specific, time window) but lacks details on pagination, limits, output format, or whether results are restricted to the authenticated user.

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 immediately conveys the action and scope with no redundancy. Front-loaded with verb 'List'.

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 no output schema, the description should clarify what information is returned (e.g., bot IDs, names, deletion dates). It does not, leaving the agent to infer. The 10-day window and 'your' provide some context, but completeness is average.

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, and the schema coverage is 100% (no parameters to describe). The description adds no param info, which is acceptable per the baseline rule for parameterless tools.

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 lists soft-deleted bots with a specific time window ('10-day backup window'), distinguishing it from sibling tools like 'list_bots' (active bots) and 'list_deleted_commands'.

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 implies use before recovery of deleted bots, but does not explicitly state when to use it or when alternatives (e.g., 'list_bots' for active bots) are better. No when-not guidance is provided.

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