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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds valuable context by detailing the returned fields (place, duration, price label, kind, page URL) and the filter, which goes beyond what the annotations provide. Pagination is not mentioned, but that is a minor omission.

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 a single sentence plus a short filter clause, with no wasted words. It could be more front-loaded with an action verb (e.g., 'Lists all offerings...') for better scanability, but it remains efficient.

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?

Given there is no output schema, the description compensates by enumerating the returned fields, and it covers the optional filter and the scope ('every'). An agent has enough information to invoke the tool correctly without further context.

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 100%, and the schema already documents the optional 'type' parameter with its allowed values. The description repeats the same values without adding new semantics like default behavior or format details, so the baseline score of 3 applies.

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 clearly states the resource (offerings) and enumerates the data fields returned, making the tool's purpose evident. However, the action verb 'list' is only implied by the tool name and title, not explicitly in the description, and it does not distinguish itself from siblings like get_offering or search.

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?

It provides the optional type filter and its allowed values, which hints at usage. But there is no explicit guidance on when to use this tool versus alternatives such as get_offering (for a single offering) or search, nor any when-not-to-use conditions.

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