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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the ordering behavior ('soonest first') and the scope ('at the shop'), which is useful context beyond the annotations. It does not disclose pagination or default behavior, but the schema covers defaults.

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?

A single, information-dense sentence that front-loads the resource and ordering, then lists the returned fields. No wasted words.

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 read-only list tool with no output schema, the description covers the resource, ordering, and return fields. It does not mention pagination or the default time window, but the schema provides defaults and the annotations cover safety. Minor gap: no explicit statement about what happens when no classes match.

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 description coverage is 67%: 'days' and 'query' have descriptions, but 'limit' does not. The description adds the meaning of the result set (date, time, price, instructor, url) but does not explain parameter semantics beyond what the schema provides. Baseline 3 is appropriate since the schema does most of the work.

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 states a specific verb ('list') and resource ('upcoming class and event sessions at the shop'), and specifies the ordering ('soonest first') and included fields (date, time, price, instructor, url). This clearly distinguishes it from sibling tools like search or get_product.

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 implies this is the tool for browsing upcoming sessions, and the sibling list (search, search_products, get_product) provides context for alternatives. However, it does not explicitly state when NOT to use it or name a specific alternative for finding classes by other criteria.

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