List Conferences

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

The 'empty list if not enabled' edge case is genuine behavioral information not derivable from annotations, and listing titles/status/join links compensates for the absence of an output schema. 'Read-only' merely restates readOnlyHint=true, and there is nothing on pagination or permission requirements.

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?

Three short sentences, front-loaded with the action, then the safety profile, then the edge case. Nothing redundant beyond the mildly duplicative 'Read-only'.

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?

With no output schema, the description correctly supplies the return shape and the disabled-feature behavior. Remaining gaps (pagination, auth/role requirements, whether recordings are included) are minor for a simple list tool.

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?

Single parameter with 100% schema coverage, where the schema already explains the numeric string format and points to list_courses as the source. The description adds no extra meaning about course_id, so baseline 3 applies.

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?

States a specific verb and resource (list web conferences) scoped to a course, names the underlying provider (BigBlueButton or similar), and enumerates the returned fields (titles, status, join links). No sibling in the list covers conferences, so disambiguation is not a concern.

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?

Implies per-course usage and warns that an empty list is returned when conferences are not enabled, which is a useful precondition. However, it never says when to reach for this versus other course-content tools (e.g. list_media_objects, list_collaborations) or whether it needs a teacher/student role.

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