get_meeting

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

No annotations are provided, so the description carries the full burden. It indicates a read operation on meeting metadata and enumerates the included data, but it does not disclose error behavior, permissions, or return format. This is acceptable for a simple get, but leaves some room for improvement.

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 one sentence, front-loaded with the core purpose, and every word adds value. It is extremely concise without losing important information.

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 one-parameter tool with no output schema, the description adequately scopes the result by listing key metadata components. It omits potential error cases or exact return shape, but given the simplicity, it is fairly complete for an agent to use 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?

Schema description coverage is 0%, and the description adds no explanation of meeting_id beyond its name. Since the tool has one parameter and the description does not compensate for the lack of schema descriptions, the agent must infer the intended meaning from the parameter name alone.

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 retrieves full metadata for one meeting, listing specific components (roster, named speakers, transcript availability, pending clarification count). This distinguishes it from siblings like list_meetings and get_transcript, which have clearly different functions.

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 gives clear context on what this tool returns, implying it should be used when detailed metadata for a specific meeting is needed. It does not explicitly mention alternatives or when not to use it, but the focus on 'one meeting' differentiates it from list_meetings and get_transcript.

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