Pilot MCP

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

With no annotations provided, the description carries full burden but discloses almost nothing. It does not define 'full content' (headers, body, attachments?), return format, rate limits, or side effects. The claim 'by ID' contradicts the empty input schema, suggesting either missing schema documentation or inaccurate description.

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 brief at six words, but underspecified given the lack of annotations and output schema. It attempts front-loading but sacrifices necessary behavioral context for brevity.

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 complex email domain with multiple sibling tools (outlook_read_email, reply_email, etc.) and no output schema or annotations, the description is insufficient. It fails to explain return values, account selection, or the relationship to other email tools.

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?

While the baseline for zero parameters is 4, the description mentions 'by ID' which implies an ID parameter that does not exist in the schema. This creates confusion about how to specify which email to read, making the description misleading rather than merely silent on parameters.

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 basic action (read email content) and implies targeting by ID, but fails to distinguish from sibling 'outlook_read_email' or clarify which email provider/account it targets. The mention of 'by ID' creates confusion since the input schema shows zero parameters.

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 versus 'outlook_read_email', 'search_emails', or 'list_emails'. Does not mention prerequisites (e.g., needing an email ID from list_emails first) or whether this marks messages as read.

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