list_meetings

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only says 'List meetings' and filters. It does not mention pagination, ordering, default visibility scope, whether filters can be combined, or any read-only guarantees. The extra sentence about meeting creation constraints adds background context but does not describe the behavior of this tool.

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 compact and front-loads the primary action and filters. The second sentence provides relevant domain context without excessive detail, though it is not essential for invoking the list operation correctly.

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 list tool with two optional parameters and no output schema, the description gives the core filters but omits important call details like whether filters are ANDed, what the default result set is, and whether status values are exact. The unsupported userId filter is a notable completeness gap that could lead to incorrect invocation attempts.

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 description adds filter context for serviceRequestId, which lacks a schema description, but it also introduces a 'participant userId' filter that is not present in the schema. Since schema coverage is only 50%, this mismatch fails to properly compensate for the undocumented parameter and can mislead the agent into passing an unsupported argument.

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 identifies the operation as listing meetings and lists filter dimensions, which distinguishes it from sibling tools like create_meeting and respond_to_meeting. However, it advertises filtering by 'participant userId' even though no such parameter exists in the input schema, which slightly muddies the intended scope.

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 implies this is the tool for listing and filtering meetings, and the sibling names make the alternative operations obvious. It does not explicitly state when to prefer this over other list tools or give exclusions, so the usage context is only implied rather than directly articulated.

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