Pilot MCP

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

With no annotations provided, the description carries full disclosure burden but fails to explain search behavior (substring vs exact match, case sensitivity), result limits, or authentication requirements. Critically, it does not address the discrepancy between described parameters and the empty schema.

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?

Single sentence efficiently conveys intent without redundancy. However, the brevity contributes to the lack of necessary context regarding schema mismatch and behavioral details.

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?

Fails to compensate for the empty input schema and lack of output schema. Missing critical context: differentiation from outlook_search_emails, explanation of the described search parameters versus actual schema, and return value description.

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?

Despite 0 parameters in the schema (baseline 4), the description explicitly references three parameters (keyword, sender, date range) that do not exist in the input schema. This creates a misleading expectation of the tool's interface and will cause invocation errors.

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?

States the core action (search emails) and identifies specific search dimensions (keyword, sender, date range) that distinguish it from simple listing tools like list_emails. However, the described parameters do not exist in the empty input schema, creating uncertainty about actual functionality.

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?

Provides no guidance on when to use this tool versus siblings like list_emails (unfiltered listing), outlook_search_emails (Outlook-specific), or read_email (direct retrieval). No prerequisites or exclusion criteria mentioned.

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