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

Annotations already declare readOnlyHint=true, and the description confirms it reads data without side effects. It adds value by detailing the returned fields (time, title, conference URL, host, alternate times), which is beyond the annotation scope.

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, well-structured sentence that front-loads the action ('Read a meeting') and efficiently conveys essential details about input and output. No extraneous words.

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 the low complexity (one parameter, no output schema, annotations present), the description provides all necessary information: input format, output fields, and read-only behavior. It is sufficiently complete for an agent to use 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?

The only parameter, meetingId, is explained in the description as 'the share-link id (the UUID from /m/<id>)'. Since schema description coverage is 0%, the description fully compensates by adding semantics that are missing from the input schema.

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 reads a meeting using its share-link ID, specifying the fields returned (time, title, conference URL, host, alternate times). This differentiates it from sibling tools like create_meeting or get_meeting_availability, making its purpose obvious.

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 mentions the input format (UUID from /m/<id>) and the fields returned, providing clear context for its use. However, it does not explicitly state when not to use it or compare it to alternatives, though the purpose is self-evident.

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