Unified Search

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds valuable context: automatic API routing based on account type, caching behavior via use_cache and force_refresh, and the safe read-only nature, exceeding what annotations provide.

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 well-structured with a lead summary, followed by details and clearly labeled Args/Returns sections. Every sentence adds value without redundancy.

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?

The description covers purpose, usage, parameters, and return format. Output schema exists, but description still summarizes return format. Missing edge cases or error handling, but sufficient for a search tool with rich annotations.

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 0% coverage (no descriptions), but the description provides clear, concise explanations for all 6 parameters, including types, defaults, and constraints (e.g., query 1-512 chars, limit 1-500). This fully compensates for missing schema descriptions.

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 it searches multiple M365 resources (emails, events, files) simultaneously, with a specific verb and resource. It distinguishes from siblings like search_emails, search_events, etc. by using 'unified' and explaining simultaneous search.

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 when to use it (multi-resource search, read-only, safe) and provides account type routing behavior. It doesn't explicitly mention alternatives but the grouping of sibling tools implies this is for combined searches.

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