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

Annotations only declare readOnlyHint, so the description carries the behavioral load and does add useful context: two distinct response modes, that only enabled items are returned, and that the rated response includes a SLIP token required by checkfront_add_to_booking_session. It still omits pagination, rate limits, and result-count behavior.

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?

Three tightly scoped sentences front-load the core purpose, then the mode-switching behavior, then the API mapping. No redundancy or filler, and the most decision-relevant fact (no dates = catalogue) is stated early.

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 13-parameter tool with a nested object and no output schema, the description covers the essential dual behavior and summarizes what the rated response returns, which is the critical missing structured information. It is not exhaustive on pagination or limits, but nothing needed to choose and call the tool correctly is absent.

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 coverage is 100%, so the baseline is 3, but the description adds a cross-parameter semantic rule not captured in the schema: start_date/end_date/param together switch the response from catalogue to rated. That interaction meaning earns a point above baseline, though the remaining filter parameters are not elaborated.

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 the enabled inventory items') and enumerates the types (tours, activities, rentals, rooms). It clarifies the two response modes and connects itself to checkfront_add_to_booking_session via the SLIP token, but does not explicitly differentiate from other list/get siblings such as checkfront_get_item or checkfront_get_availability_calendar.

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?

Gives clear conditional guidance: no dates yields the plain catalogue, passing start_date (plus end_date/param) yields a rated response with availability and pricing. It does not state when to prefer an alternative tool or any exclusions, so it stops short of full when/when-not guidance.

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