list_bookings

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds useful behavioral context: the result set is limited to bookings the instance created or changed, and results are sorted newest first. It does not clarify the meaning of 'lashing instance' or address pagination/limits, but with annotations present this is acceptable though minimal.

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?

The description is one short sentence with no filler, front-loading the resource and then adding scope and ordering. The unusual word 'lashing' slightly obscures the message but not enough to lower the conciseness score below 4.

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 zero-parameter read-only tool with an output schema, the description covers what is needed: entity type, scope, and ordering. The only gap is the unexplained 'lashing instance' qualifier, which likely relies on domain knowledge.

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 schema has zero parameters, so there is no parameter meaning to add beyond what the schema already defines. The baseline for zero-parameter tools is 4, and the description's scope and ordering notes do not conflict with that baseline.

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 phrase 'Bookings this lashing instance has created or changed' identifies a scoped list resource and distinguishes it from get_booking and propose_booking by focusing on bookings the instance itself created or modified. It lacks an explicit verb like 'List', and the term 'lashing instance' is opaque, preventing a top score.

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?

The description implies when to use it: when you need bookings created or changed by this instance, newest first. It provides no explicit alternatives, exclusions, or when-not-to-use guidance relative to siblings such as get_booking or list_plans.

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