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

With no annotations, the description carries the full burden of behavioral disclosure. It only states that the tool searches Outlook emails, but omits critical details such as return format, pagination, authentication requirements, or query syntax. This lack of transparency leaves the agent guessing about the tool's 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 short (one sentence), but this is under-specification rather than effective conciseness. It lacks essential details such as search scope, result ordering, or limitations, so the brevity does not serve the user's needs.

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 tool has two parameters, no output schema, and many similar sibling tools, the description is severely incomplete. It does not explain what 'Search Outlook emails' returns, how to use parameters, or how it differs from alternatives like 'search_email' or 'get_outlook_inbox', making it inadequate for an agent to invoke correctly.

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 input schema has two parameters (q and limit) with 0% schema coverage and no descriptions in the tool description. The description does not mention or explain these parameters, adding no meaning beyond the bare names. Since the schema provides no help and the description provides none, the semantic value is minimal.

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 states a specific verb ('Search') and resource ('Outlook emails'), making the core function clear. However, it does not distinguish from sibling tools like 'search_email' or 'get_outlook_inbox', which may cause confusion about when to use this tool over similar alternatives.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention any specific use cases, prerequisites, or comparison with sibling tools like 'search_email' or 'get_outlook_inbox', leaving the agent without direction.

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