List Appointment Groups

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

Beyond the readOnlyHint and idempotentHint annotations, the description adds the key behavioral nuance that results are limited to groups with open time slots by default, and directs the agent to the booking tool. It does not describe result shape/pagination, but the tool's read-only nature limits the risk of misuse.

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 compact sentences: the first defines the resource and its useful payload, the second gives the read-only guarantee and the next-step tool. Nothing is wasted and the core purpose is front-loaded.

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 zero-required-parameter read-only list tool with fully documented schema, the description covers purpose, default filtering behavior, and the follow-up action. The only omission is any mention that a `manageable` scope exists for organizers, which the schema handles.

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?

The description covers the defaulted behavior of the key filter by scoping to groups the agent can 'sign up for' with open slots, which aligns with the `signup` default. It says nothing about the alternate mode (manageable groups) or `include_past`, but since schema coverage is 100% and those are documented in the schema, this adds a useful behavioral anchor without redundancy.

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 appointment groups") and qualifies the scope as groups the user can sign up for with open time slots, with concrete examples (office hours, advising). This is clearly distinguishable from the sibling get_appointment_group, which fetches a single group.

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?

Explicitly names the follow-on action tool (reserve_appointment_slot) so the agent knows this is the discovery step before booking. It does not, however, state when not to use it (e.g. for managing existing reservations, where list_my_reservations applies).

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