Pilot MCP

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers none. It does not specify which folder is queried (Inbox, All, Sent), volume limits, pagination behavior, or whether the operation is read-only, leaving critical operational context undefined.

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 at six words with no redundant phrasing. However, given the absence of an output schema and annotations, this brevity contributes to under-specification rather than efficient communication of necessary context.

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 lack of annotations and output schema, the description fails to provide essential context such as return value structure, email field inclusion, or folder scoping. For a tool interacting with an external email service, this level of description is inadequate for confident 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?

The input schema contains zero parameters, establishing a baseline score of 4. The description does not need to compensate for missing parameter documentation, though it could have clarified that the tool uses default mailbox settings due to the lack of filtering options.

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 the basic action (List) and resource (emails from Microsoft Outlook), but remains vague about the scope and return format. It fails to differentiate from siblings like `outlook_search_emails` or `list_emails`, leaving ambiguity about whether this retrieves full content, headers, or just IDs.

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 `outlook_search_emails` (which likely supports filtering) or the generic `list_emails`. There are no stated prerequisites, such as requiring authentication or specific Outlook folder selection.

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