trending_booking_status

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

With no annotations, the description carries the full burden. It usefully discloses the set of expected status values, which helps interpret results, but it never states that this is a read-only lookup, what permissions are needed, or what happens if the booking is not found.

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 front-loaded sentence with the resource stated first and the state enumeration parenthetically. Efficient and free of filler, though it is arguably too terse for the ambiguity it leaves.

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?

No annotations, no output schema, and three undocumented optional parameters mean the description is the only source of behavioral detail, and it supplies little beyond the status names. It does not explain the return shape or how to resolve a booking.

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?

Three parameters exist with 0% schema description coverage, and the description adds no meaning for any of them. It does not clarify whether bookingId is required, how chain and tokenAddress relate to it, or which combination identifies a booking, leaving the caller to guess.

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 ('Check trending-slot booking status') and even enumerates the possible states (pending payment, active, expired). However, it does not distinguish itself from nearby siblings such as managed_trade_status or trending_register, so an agent can't tell which status-checking tool applies without opening schemas.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative. The description never says whether a booking is identified by bookingId, tokenAddress, or chain, which is the key usage decision for this tool.

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