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

Annotations already declare read-only, idempotent, closed-world, and non-destructive behavior. The description adds useful behavioral context beyond annotations: notes are limited to what "the person may read," and other-side form answers appear only "where the programme shares them," plus it discloses cancellability information.

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?

It is a single dense sentence with a front-loaded "One meeting:" label and no obvious filler. The long colon-chain is harder to scan than a short list, but the length is largely justified because there is no output schema and the description must enumerate return content.

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 carries the burden of explaining return content, and it does so by naming the meeting fields, note access rules, and form visibility. Remaining gaps are minor, such as not-found behavior and exact response shape.

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 100%, and the sole parameter meeting_id is fully documented in the schema. The description adds no additional format, source, or lookup guidance for the meeting ID.

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 opens with "One meeting:" and enumerates the attributes returned: time, place or video link, who, goal, cancellability, notes, and programme forms. This makes the resource and read scope clear, though the retrieval verb is implied by the tool name rather than explicitly stated.

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 single-meeting focus and required meeting_id imply use when details for a known meeting are needed. However, it never explicitly contrasts with list_meetings or find_meeting_slots, nor does it 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.