timeiq_time_delete_many

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

No annotations exist, so the description must disclose behaviors. It mentions a safeguard but does not explain what happens when the limit is exceeded, whether confirm_bulk is required, or if the deletion is permanent. Missing auth requirements, rate limits, and return behavior.

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 extremely concise (12 words), but it underspecifies the tool's behavior. It is front-loaded but lacks structure and detail for a 4-parameter tool. Conciseness is not a virtue when it omits critical information.

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 presence of sibling tools for single delete, batch update, and expense delete, the description lacks context about when to use this tool. No output schema, no parameter descriptions, and no mention of return values or error conditions. Incomplete for effective selection and invocation.

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 description coverage is 0%, so the description should clarify parameter meaning. It only alludes to the safeguard (likely confirm_bulk), but does not explain dry_run (test mode) or requesting_slack_id (audit). The description adds minimal value beyond param names.

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 action ('Delete'), resource ('multiple time entries'), and a key feature ('safe-guarded for actions exceeding 50 entries'). It differentiates from siblings like timeiq_time_delete (single) and timeiq_expense_delete_many (different resource).

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 indicates it is for bulk deletion with a safeguard, but does not explicitly state when to prefer this over timeiq_time_delete or timeiq_time_batch. No exclusions or alternatives are provided, leaving some ambiguity.

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