Get Outlook Meetings

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

With no annotations, the description carries the full burden and does disclose real behavioral context: it requires AZURE_CLIENT_ID configuration to be enabled and triggers a first-run device-code auth flow. What it omits is the read-only safety profile and any error/empty-calendar behavior, but the auth onboarding disclosure is substantive beyond a bare verb.

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?

Three short paragraphs, front-loaded with the core action, followed by the setup prerequisite and the return-format reference. Every sentence is relevant, though the auth paragraph is slightly more operational detail than selection guidance.

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?

An output schema exists, so the description needn't explain return values, and the one optional parameter is fully covered by the schema. The auth prerequisite is surfaced, leaving only minor gaps around read-only semantics and failure modes for a tool with no annotations.

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?

Schema description coverage is 100%, so hours_ahead and its 24-hour default are already fully documented in the schema. The description adds no supplementary syntax or boundary detail beyond that, which is the expected baseline when structured data does the work.

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 a specific verb and resource (get upcoming meetings from Outlook/Microsoft 365 calendar) and disambiguates the data source from the Google variant by naming get_upcoming_meetings as the format reference. An agent can tell which calendar backend this targets, though it doesn't explicitly say it is the Outlook counterpart to use instead of the Google tool.

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?

The source qualifier (Outlook/Microsoft 365) implies when this tool is appropriate versus get_upcoming_meetings, and the AZURE_CLIENT_ID line implies a precondition. However, there is no explicit when-to-use/when-not statement nor a direct routing sentence pointing to alternatives.

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