meetings_list

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While 'List all meetings' implies a read operation, it doesn't specify whether this requires authentication, has rate limits, returns paginated results, or what happens when no meetings exist. The description lacks crucial behavioral context for a tool with 5 parameters.

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 appropriately concise at 6 words, front-loading the core purpose. However, it could be more structured by explicitly mentioning key parameters or distinguishing from siblings, though it avoids unnecessary verbosity.

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 tool with 5 parameters, 0% schema coverage, no annotations, and no output schema, the description is inadequate. It doesn't explain parameter usage, return format, error conditions, or how it differs from similar tools. The minimal description leaves too many gaps for effective agent use.

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 all 5 parameters, the description must compensate but fails to do so. 'Optional filtering' vaguely references parameters but doesn't explain what 'after', 'limit', 'createdAfter', 'createdBefore', or 'properties' mean or how they work. The description adds minimal value beyond what the bare schema provides.

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'), making the basic purpose understandable. However, it doesn't differentiate from sibling tools like 'meetings_search' or 'meetings_get', leaving ambiguity about when to use this specific listing tool versus search or retrieval alternatives.

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. With sibling tools like 'meetings_search' and 'meetings_get' available, the agent receives no indication whether this is for bulk listing, filtered listing, or basic retrieval. The mention of 'optional filtering' is too vague to serve as meaningful usage guidance.

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