Read Luca-managed call slots

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description still adds real value beyond them: that conflicts are pre-filtered out of the results, the OAuth scope requirement (luca:read), the data-sensitivity/redaction note, and that no idempotency key is needed.

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 key capability is front-loaded in the first sentence and the remaining lines are short metadata bullets. The 'Luca operation' and 'Does not require idempotency' lines are borderline boilerplate but compact, so nothing meaningfully bloats the definition.

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?

An output schema exists, so return values need no explanation, and annotations plus the scope/workspace notes cover most operational prerequisites. What is missing is the disambiguation from luca_bookings_availability and any indication of time-range defaults or limits for a slot-listing call.

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%, so the schema does much of the work. The description explains the workspaceId/workspaceSlug override semantics and the environment-configured default, which goes slightly beyond the schema's terse 'Optional Luca workspace id override'. The required nested query fields (bookingTypeId, timezone, start/end) receive no explanation of format or defaults.

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 names a specific verb and resource — 'List open slots for one of Luca's own call types' — and adds the meaningful qualifier that calendar conflicts are already removed. It is clear on its own, but it never differentiates itself from the very similar sibling luca_bookings_availability, so an agent must guess which of the two to call.

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?

Usage is implied ('list open slots for one of Luca's own call types'), and the description adds prerequisite context via required scopes. However there is no explicit when-to-use vs when-not guidance and no mention of the near-identical luca_bookings_availability alternative, which is the single most important routing decision here.

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