list_meetings

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

No annotations provided, so description carries full burden. It does not explicitly state that the tool is read-only, nor does it mention any side effects, auth requirements, or rate limits. The parameter descriptions add some context but behavioral traits are under-described.

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?

Description includes a stray 'ctx: MCP context' line that does not correspond to any parameter in the input schema, creating inconsistency. It is moderately concise but the extra line wastes space and may confuse.

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 6 parameters and no annotations, description covers parameter meanings and return type ('Paginated list of meetings'). However, it lacks details on pagination behavior, error handling, and date format restrictions. With an output schema present, some of this is likely covered, but not guaranteed.

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%, but description provides a docstring-style explanation of each parameter, including defaults and expected format (e.g., YYYY-MM-DD for dates). This adds significant meaning beyond the bare 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?

Description clearly states 'List meetings with optional filters', which is a specific verb and resource. However, it does not explicitly distinguish from sibling tools like search_meetings, but the purpose is still clear.

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?

Description implies usage by showing filter parameters but provides no guidance on when to use list_meetings vs search_meetings or other siblings. No 'when to use' or 'when not to use' information.

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