easytable_list_times

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

The description is consistent with the readOnlyHint annotation by describing a read-only listing operation. It also adds useful behavioral detail beyond the annotation: times are returned as HH:MM. No destructive or hidden behavior is suggested.

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?

The description is two short sentences with no redundant phrasing. The core purpose is front-loaded, and the output format detail is placed directly after the main action.

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?

The description explains the tool's inputs and the time format, and the read-only annotation covers safety. Since there is no output schema, mentioning 'Times are returned as HH:MM' partially fills the return-value gap, though it does not describe the exact response container or empty-result behavior.

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 schema already documents most parameters well (id, date, lang, type), and the description adds meaning to the otherwise undocumented persons parameter by calling it 'party size'. It also clarifies that 'type' refers to a restaurant area. With 80% schema coverage, this is a meaningful but not critical addition.

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 a clear resource: available time slots for a restaurant area, date, and party size. It also adds the output format (HH:MM), which disambiguates this from sibling tools like easytable_list_types and easytable_list_dates.

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 makes the tool's purpose clear: use it when you need available time slots given area, date, and party size. It does not explicitly explain when not to use it or name an alternative like easytable_find_bookings, but the context is strong enough for an agent to infer the appropriate usage.

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