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

With no annotations, the description carries the full burden of behavioral disclosure. It implies a read scoped to 'the token holder' (some auth context), but it never states read-only semantics, what happens for an unknown booking_id, or whether errors are returned versus empty results.

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 compact sentence that front-loads the resource and then lists the returned data. It is efficient, though the fragmentary style omits a verb and reads as a field list rather than a full statement.

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 one-parameter lookup with no annotations and no output schema, the description should at minimum explain what booking_id is and confirm the read behavior. It instead leaves the sole parameter entirely undocumented, so the definition is not sufficient to call the tool correctly.

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?

The single required parameter booking_id has 0% schema description coverage, so the description must define it, but it never mentions the parameter at all. No format, source, or validation hints are given, so the coverage gap is uncompensated.

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 the resource (booking) and enumerates the returned fields (escrow state, amount, confirmation code), so the agent can infer this is a status lookup. However, there is no verb and no explicit statement that it retrieves rather than creates or mutates a booking, leaving it only loosely distinguishable from the sibling everlist_book.

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 use this tool versus alternatives such as everlist_book or everlist_contract, and no preconditions or exclusions are stated. The agent must infer usage entirely from the name and the field list.

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