List my web conferences

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds valuable context beyond that: it returns join links, covers live/scheduled sessions, and clarifies the distinction from calendar events. It does not mention pagination or response format, but the safety profile is well covered by annotations.

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?

Two sentences with zero waste. The core purpose is front-loaded, and the calendar distinction is included in the same breath. Every word earns its place.

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 simple read-only list tool with no output schema, the description is near-complete. It mentions scope (all courses or one), join links, and the calendar distinction. It does not mention pagination or rate limits, but these are not critical for a tool of this simplicity and the annotations already establish safety.

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 coverage is 100%, with both parameters described in the schema. The description adds marginal value by implying the state filter ('live' only) and the courseId scope, but it does not elaborate on parameter syntax or behavior beyond what the schema already states. Baseline 3 is appropriate.

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 states the tool lists web conferences (BigBlueButton class sessions) with join links, across all courses or one course. It explicitly differentiates itself from calendar events, making its purpose unambiguous and distinct from sibling tools.

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 clear guidance on when to use it: 'These are NOT in the calendar, so use this to catch live class sessions.' It implies the alternative (calendar events) and gives a specific use case. However, it does not explicitly name other tools or provide exclusions beyond the calendar distinction.

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