List services

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

The readOnlyHint annotation already establishes the safety profile, so the description only needs to add context on top. It contributes the dependency signal ('call this first') and effectively describes what comes back, which matters since there is no output schema, but it says nothing about result volume, format, or whether the response is cached/static.

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 fragments, no waste, and the payoff directive is easy to spot. The telegraphic style omits a subject/verb, which slightly reduces readability but keeps it maximally compact.

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 no output schema, the description covers both what the caller receives and when to call it. The only real gap is that it does not describe the shape or size of the returned data, which would help an agent plan follow-up calls.

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 tool takes no parameters, so per the baseline there is nothing for the description to disambiguate. Nothing in the description misleads about inputs.

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 is a noun phrase enumerating the data domains returned (services, prices, staff, opening hours, booking rules) rather than stating an action with a verb, so the agent must infer from the name that this retrieves rather than configures them. It does implicitly distinguish itself from the booking siblings by covering reference data rather than bookings, but the framing is vague about whether it returns a list of services or a full configuration bundle.

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?

'Call this first' is an explicit, actionable sequencing directive that tells the agent to bootstrap with this tool before the booking siblings. There is no statement of when not to call it or of alternatives, but for a zero-parameter reference tool that exclusion is largely unnecessary.

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