find-meeting-rooms

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

The description adds context beyond annotations: it specifies the endpoint (Graph rooms), read-only behavior is reinforced, and it reveals M365-only limitation and outputVerbosity impact. This gives useful behavioral insights not present in the readOnlyHint annotation.

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 concise (three sentences) and front-loaded with purpose, then return fields, filtering, and caveats. Every sentence adds value without redundancy.

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 5 parameters, no output schema, and read-only annotation, the description covers purpose, return fields, filtering semantics, platform limitation, and output verbosity. It provides enough context for an agent to select and invoke the tool correctly.

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?

Although schema coverage is 100%, the description adds semantic value by explaining that query matches name/email, capacity is 'minimum', and outputVerbosity controls field count. These clarifications go beyond the schema descriptions.

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 clearly states the tool discovers bookable meeting rooms via the Graph rooms endpoint, with a specific verb ('Discover') and resource ('meeting rooms'). It also distinguishes itself from siblings by focusing on room discovery and explicitly notes suitability for piping into create-event, which differentiates it from other tools.

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 description gives explicit when-to-use guidance: it mentions piping into create-event as attendees and provides filtering options (query, building, floor, capacity). It also includes an exclusion scenario ('Returns empty list on personal accounts'), which serves as a when-not-to-use note.

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