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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered by structured data. The description adds the extra nuance that the result confers no reservation or bookability, which is genuinely useful context, but says nothing about auth needs, rate limits, or the 'when one exists' empty-result case.

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?

Two short sentences, front-loaded with the positive behavior and closed with the important caveat. No filler.

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?

An output schema exists, so return values needn't be described, and the 'when one exists' phrasing sensibly flags a possibly-absent result. However, the opaque 'publicReference' input and the lack of any indication of what a listing reference refers to leave a gap an agent must guess at.

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 the single required parameter 'publicReference', and the description never explains what form that reference takes or where it comes from. With one undocumented parameter, the description fails to compensate for the coverage gap.

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: it 'returns' the listing's 'actual catalogue services'. The conditional 'when one exists' qualifies the scope sensibly. It does not explicitly differentiate itself from siblings, though none of the listed siblings appear to overlap on catalogue services.

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?

Provides a negative guideline - 'Does not reserve a slot or claim bookability' - which usefully narrows expectations, but it does not say when to reach for this tool versus an alternative, nor name any sibling. Usage is implied rather than directed.

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