trending_booking_status

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered by structured data. The description adds value by disclosing the enumerated status lifecycle (pending payment, active, expired), but says nothing about authorization requirements, what happens if the booking does not exist, or whether results are scoped per chain.

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 sentence with the verb front-loaded and the status enumeration as a compact parenthetical. Nothing is wasted, though the tightness borders on under-specification given the undocumented parameters.

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?

With three parameters at 0% coverage, no required fields, no output schema, and no parameter explanation, an agent cannot reliably construct a call. The description should at minimum state which identifiers to supply and how they combine, but it stops at naming the resource.

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% for all three parameters (chain, bookingId, tokenAddress), so the description carries the full burden — and it mentions none of them. It never explains whether bookingId or tokenAddress is the lookup key, what chain accepts, or why all three are optional.

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+resource ('Check trending-slot booking status') and enumerates the possible states (pending payment, active, expired). It is clear what the tool returns, though it does not differentiate itself from nearby siblings like trending_list, trending_register, or managed_trade_status.

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?

No guidance on when to call this versus alternatives, no mention of prerequisites (e.g., that a booking must have been created via trending_register), and no indication of which identifiers are needed. The agent must infer the entire usage context.

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