meeting_followup_select_past_meeting

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

With no annotations provided, the description should disclose behavioral traits. It does not mention whether the operation is read-only, what happens if the meeting ID is not found, or any side effects beyond storing output. The description is minimal and lacks transparency.

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 sentence of 15 words, front-loading the action. Every word is necessary and it avoids fluff or repetition. It is appropriately sized for the tool's simplicity.

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 tool's simplicity, the description is minimally complete: it states the purpose and relies on the schema for parameters. However, it lacks details about the output format (e.g., what details are stored in the variable) and error handling. The absence of an output schema increases the need for description, which is not met.

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%, so the schema already describes all parameters clearly. The description adds only the phrase 'based on the meeting ID', which is redundant with the parameter description. It does not provide additional meaning beyond the 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 'Extracts the selected meeting from a list of past calendar events based on the meeting ID' uses a specific verb ('Extracts') and resource ('selected meeting from a list of past calendar events'), clearly distinguishing it from sibling tools like meeting_followup_analyze_transcript or meeting_prep_extract_selected_meeting.

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 provides no guidance on when to use this tool vs alternatives such as meeting_prep_extract_selected_meeting, nor does it mention prerequisites like first calling get_calendar_events_list. Usage context is implied but not explicit.

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