find-meeting-rooms

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

The annotations already provide readOnlyHint=true, but the description adds important behavioral context: the endpoint is M365-only, returns empty on personal accounts, and specifies the output fields. This goes beyond the annotation by explaining limitations and return structure, aiding agent understanding.

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 (4 sentences), front-loaded with the core purpose, then details returns, filtering, limitations, and output control. Every sentence adds value with no redundancy, making it easy to scan and understand.

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 lacking an output schema, the description lists the returned fields (displayName, emailAddress, etc.) and covers all key aspects: source, filtering, limitation, and output verbosity. It is nearly complete for this tool, though it could mention pagination or ordering if applicable.

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 coverage is 100%, so the baseline is 3. The description mentions all parameters and adds minor clarifications (e.g., 'minimum' for capacity, 'field count' for outputVerbosity). However, it largely repeats schema descriptions, providing no significant new meaning.

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 read-only access. It explicitly lists the returned fields and distinguishes itself from sibling tools like create-event and search-people by indicating it is suitable for piping into events and is for rooms only.

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 provides good usage context: it is suitable for feeding into create-event and notes that it returns empty on personal accounts (M365-only). While it doesn't explicitly list alternatives or when not to use it, the guidance on piping to create-event and the account limitation are helpful for correct tool selection.

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