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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds genuinely new behavioral facts beyond those hints: it explicitly does not join a room or mint participant credentials, and it specifies that both URL variants must always be included when links are requested. No mutation, auth, or rate-limit details, but the negative-capability disclosure is the value here.

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?

Front-loaded with the read action and the returned payload, then the prerequisites and the link-formatting rule. Every sentence carries information; the link-labelling instruction is slightly prescriptive but tied to real output behavior.

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, the description compensates by listing the returned fields and both URL variants, and annotations carry the safety profile. Missing only edge details such as what happens for an unknown or non-owned roomId, but the essentials for calling it correctly are present.

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 0%, so the description carries the burden. It usefully explains the source of roomId ("Resolve ... with list_meetings first"), but says nothing explicit about the locale parameter's role beyond the incidental phrase "in the user's language". One of two parameters is effectively undocumented.

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 ("Read one owned My business meeting") and enumerates exactly what is returned: title, schedule, current status, settings, guestUrl/hostJoinUrl. An agent can distinguish it from list_meetings and get_meeting_catchup without opening any schema.

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?

Explicitly routes the agent: "Resolve the roomId with list_meetings first" names the prerequisite tool and the condition. It also carves out what this tool is NOT for ("Does not join the room or generate participant credentials"), implicitly pointing to the joining flow rather than leaving the boundary to inference.

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