get-online-meeting

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

The annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds which meeting fields are included, but it does not disclose behavioral details like not-found behavior or response shape. Given the annotations, this is adequate but not exceptional.

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 a single, focused sentence with no redundant phrasing. The verb, resource, lookup key, and expected fields are all front-loaded, making it easy for an agent to parse quickly.

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?

For a simple read-only get-by-id tool with one clearly described parameter, the description is nearly complete. It covers the lookup key and returned fields. It could be improved by explicitly noting that it returns a single meeting object or by directing users to find-online-meeting-by-join-url when only a join URL is available.

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%, but the schema's description for meetingId is just 'Value for meetingId', which is uninformative. The tool description adds real meaning by clarifying that the parameter is an onlineMeeting id and indicating the data associated with it.

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 uses a specific verb ('Get'), names the exact resource ('online meeting'), and specifies the lookup key ('onlineMeeting id'). It also lists the key fields returned, making the tool's purpose unmistakable and distinguishing it from sibling tools like find-online-meeting-by-join-url.

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 implies this tool should be used when the caller already has an onlineMeeting id, which is clear context. However, it does not explicitly mention alternatives such as find-online-meeting-by-join-url or state when not to use this tool.

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