meetings_batch_archive

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

No annotations are provided, so the description carries full burden. While 'archive (delete)' clearly indicates a destructive operation, the description lacks critical behavioral details: whether this is permanent or reversible, what permissions are required, whether it affects associated data, error handling for partial failures, or rate limits. For a destructive batch operation with zero annotation coverage, this is insufficient.

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, efficient sentence that communicates the core functionality without unnecessary words. It's front-loaded with the key action and resource, making it immediately scannable and understandable.

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 destructive batch operation with no annotations and no output schema, the description is inadequate. It doesn't address critical context like: what 'archive' means (permanent deletion vs. soft delete), whether the operation is atomic, what happens to associated resources, error responses, or success criteria. The agent would be operating with significant uncertainty about this tool's behavior.

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 description mentions 'multiple meetings' which implies the 'meetingIds' parameter, but with 0% schema description coverage, it doesn't explain the format of meeting IDs, whether there are limits on batch size, or validation requirements. The description adds minimal value beyond what's obvious from the parameter name, meeting the baseline for a single-parameter tool.

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 ('archive (delete)') and resource ('multiple meetings'), making the purpose immediately understandable. However, it doesn't explicitly distinguish this tool from its sibling 'meetings_archive' (single meeting archive) or other batch archive tools like 'calls_batch_archive', leaving some ambiguity about when to choose this specific batch tool.

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 provides no guidance on when to use this tool versus alternatives. With multiple sibling tools including 'meetings_archive' (single meeting), 'meetings_batch_create', and other batch operations, there's no indication of when batch archiving is preferred over individual archiving or how this differs from similar batch operations on other resources.

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