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

readOnlyHint=true already tells the agent this is a safe read, so the description only needs to add context. It does add useful detail (the fields each lesson carries and the underlying GET /lessons endpoint) but says nothing about pagination behavior, result size, or what happens with deleted/series records even though page/per_page/include_deleted/series_id exist.

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 purpose, then filters, then endpoint. No filler and nothing repeated verbatim from the schema.

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 usefully enumerates the returned fields, and annotations cover the safety profile. For a 17-parameter listing tool it is largely complete, though it omits pagination and sort behavior that an agent would want to know.

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 94%, so the schema already documents nearly all 17 parameters, including the subtle date_from vs from_date vs date_to and location_id vs location_or_parent_location_id distinctions. The description only repeats high-level filter categories, adding no meaning beyond the schema — the baseline 3.

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 (List) and resource (lessons), and enumerates the fields returned (teacher, service, location, start/end, duration, status, participants) plus the supported filters. It is clearly the collection counterpart to teachworks_get_lesson, but it never names a sibling, so differentiation is implicit rather than stated.

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 filter list implies when this tool is useful (browsing/searching lessons by criteria), but there is no explicit when-to-use guidance and no mention of alternatives such as teachworks_get_lesson for a single lesson or teachworks_list_other_events for non-lesson calendar items.

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