Pilot MCP

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

No annotations provided, so description carries full burden. The word 'List' implies read-only, but description lacks pagination details, default date ranges (since schema has 0 params), rate limits, or whether it returns full event details vs. summaries.

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?

Extremely brief (3 words), which technically avoids verbosity, but constitutes under-specification rather than efficient communication. No structural issues, but content is insufficient for the format.

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?

With no output schema and no annotations, the description should explain return format, default behavior (what time range is returned?), and any implicit limits. It provides none of this context.

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 has 0 parameters, so baseline score applies per rubric. Description neither adds nor subtracts value regarding parameters since none exist.

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 (List) and resource (Outlook calendar events), but fails to distinguish from sibling tool 'list_calendar_events' (likely Apple Calendar) or clarify scope (upcoming vs. all events, date ranges).

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 'list_calendar_events', 'outlook_search_emails', or 'outlook_create_event'. No mention of prerequisites or filtering capabilities.

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