Pilot MCP

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

No annotations are provided, so the description carries full burden of behavioral disclosure. It fails to explain which email is read (critical given the empty parameter schema), whether the operation marks emails as read, or what data structure is returned.

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 brief at four words, but this conciseness comes at the cost of utility. While not verbose, it fails to front-load critical context about the tool's operation or identifier requirements.

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?

Despite low complexity (zero parameters), the description is incomplete. It does not resolve the ambiguity of how the target email is specified given the empty input schema, nor does it describe return values or side effects expected from an email reading operation.

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?

Input schema contains zero parameters. Per evaluation rules, 0 params = baseline 4. There are no parameters requiring semantic clarification.

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 'Read an Outlook email' is a tautology that restates the tool name. It fails to specify what 'read' entails (fetch body, metadata, attachments?) or distinguish from sibling tools like read_email (generic) vs outlook_list_emails.

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 provided on when to use this tool versus alternatives like read_email, outlook_search_emails, or outlook_list_emails. The description does not indicate prerequisites or selection criteria.

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