meetings_list

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a list operation with optional filtering, but doesn't mention whether this is a read-only operation, what permissions might be required, whether results are paginated, or any rate limits. The description is minimal and leaves critical behavioral aspects unspecified.

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 extremely concise - a single 7-word sentence that efficiently communicates the core purpose. It's front-loaded with the main action and resource. However, for a tool with 5 parameters and no annotations, this brevity comes at the cost of completeness.

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 5 parameters with 0% schema coverage, no annotations, no output schema, and multiple sibling tools with overlapping functionality, the description is insufficiently complete. It doesn't help an agent understand how to properly invoke this tool versus alternatives, what the parameters mean, or what behavior to expect from the operation.

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?

With 0% schema description coverage for 5 parameters, the description doesn't compensate by explaining what the parameters mean. It mentions 'optional filtering' but doesn't specify which parameters provide filtering, what 'after', 'createdAfter', 'createdBefore', 'limit', or 'properties' mean, or how they should be used. The description adds minimal value 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?

The description 'List all meetings with optional filtering' clearly states the verb ('List') and resource ('meetings'), and specifies the scope ('all') with optional filtering. However, it doesn't differentiate from sibling tools like 'meetings_search' or 'meetings_get', which appear to serve similar purposes in the same domain.

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 versus alternatives like 'meetings_search' or 'meetings_get'. It mentions optional filtering but doesn't specify what types of filtering are available or when to choose this over other meeting-related tools in the sibling list.

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