outlook_batch_triage

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

With no annotations, the description explains the batch call, hard cap, and action parameters. It does not mention error handling, authorization needs, or return behavior, but the basic behavior is clear. No contradiction with annotations.

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?

Two sentences plus an example. Every sentence adds value. Information is front-loaded with action parameter details and a concrete example. No wasted words.

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?

Tool has no output schema and no annotations. Description covers input parameters, cap limit, and example. Missing output description (e.g., success/failure per message). Adequate but not fully complete.

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 coverage is 0%, but description fully explains all three parameters: message_ids (list), action (four values), value (target folder/status/category). Includes an example. Adds significant meaning beyond the bare schema.

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 performs batch triage on up to 20 messages, listing actions like 'move', 'flag', 'categorize', 'mark_read'. The verb 'triage' is somewhat vague but is clarified by the action list. It distinguishes itself from individual action tools by emphasizing batching.

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 for performing the same action on multiple messages, and notes a cap of 20. However, it does not explicitly state when to use this tool versus individual tools like outlook_move_message, nor mention when not to use it.

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