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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=true, so the mutation/repeat-safety profile is covered. The description adds genuine non-annotation context — that future classes are auto-generated up to the booking horizon — but never explains what the destructiveHint=true actually destroys (e.g. overwritten existing sessions).

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 short sentences with the access constraint front-loaded and no filler; every clause carries information.

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 destructive, non-read-only mutation tool with a complex nested schedule parameter, no output schema, and only 33% schema coverage, the description is too thin. It omits how the schedule is structured, what happens to existing sessions, and the meaning of the booking horizon.

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 only 33%, and the description contributes nothing about parameters. It does not explain the nested 'schedule' array structure (days/time/capacity/duration_min/capacity_online), the accepted day formats, or the role of offering_id, so the coverage gap is not compensated.

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 clear action and resource: it sets when a class runs (a class timetable), and the name/verb 'upsert' is reflected in 'Set'. However, it does not differentiate from the very similar sibling 'owner_set_schedule', so an agent cannot tell which one to pick from purpose alone.

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?

It gives an audience constraint ('Only for business owners signed in to Awning'), which implies the usage context, but there is no when-to-use vs alternatives guidance. The near-identical siblings 'owner_set_schedule' and 'owner_add_offering' are never mentioned.

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