list_appointments

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

With no annotations, the description carries the full burden. It does disclose two real behavioral traits an empty schema cannot convey: the results are scoped to the authenticated patient (no user parameter) and filtered to 'upcoming' appointments only. However, it says nothing about ordering, result limits, or the session/auth requirement implied by the ichilov_login siblings.

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 sentence fragment with zero filler, front-loaded on the resource being returned. It is arguably under-specified rather than over-long, so conciseness itself is good.

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-parameter list tool with no output schema and no annotations, the description covers what is returned but not how: no return-field structure, ordering, or session prerequisite. It is minimally adequate but leaves the auth dependency (evident from the login siblings) unstated.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The absence of any filtering parameters (date range, department) is consistent with the 'upcoming' scoping stated in the description.

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?

Names the specific resource (appointments) with two scoping qualifiers: 'the patient's' and 'upcoming', plus the location. An agent can tell this retrieves the current patient's future appointments, and it is clearly distinct from the sibling list_documents. It loses a point for being a noun phrase rather than an explicit verb+resource statement.

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?

No when-to-use or when-not-to-use guidance is given, and no alternatives are named. The only routing signal is implicit: sibling names like ichilov_login suggest a session may need to exist first, but the description never says so.

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