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

The annotation only declares readOnlyHint=true, and the description adds meaningful context beyond it: results are scoped to Beijing time, results are filtered to exclude booker identity, activity-private data, and contact details, and the absence of occupancy must not be read as a confirmed reservation. It does not describe the response shape (free/busy blocks, granularity, or pagination), which is the remaining behavioral gap.

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 with zero filler; the date/timezone scope is front-loaded and the privacy limitation plus the confirmation caveat each add distinct value. Nothing is repeated from the schema or annotations.

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?

There is no output schema and no annotation coverage beyond readOnlyHint, and the definition never indicates what an availability result looks like or what units/granularity the occupancy is reported in. It also omits any explanation of two of the three required parameters, leaving an agent under-equipped for a tool with fully required inputs and an undefined return payload.

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 0%, so the description must carry the burden of explaining the three parameters. It clarifies only `date` (Beijing-time YYYY-MM-DD), leaving `venueId` and `organizationId` — including the unusual $ref relationship where venueId reuses the organizationId definition — completely unexplained in either structured data or prose.

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 action and resource: viewing venue occupancy for a given Beijing-time date in YYYY-MM-DD format. It is clear enough to act on, but it does not distinguish itself from nearby siblings such as manage_ecosystem_venue_bookings, list_ecosystem_venues, or search_venues, so an agent must infer that this tool is the read-only availability check rather than the booking manager.

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 only implied: the caveat 'no occupancy does not mean the booking is confirmed' suggests this is a pre-booking availability probe, but the description never states when to call it versus manage_ecosystem_venue_bookings or search_venues. There are no explicit exclusions or prerequisite conditions beyond the date format.

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