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

No annotations are provided, so the description carries the burden. It makes clear this is a passive informational lookup rather than an action, and warns against misuse as a diagnostic. It doesn't explicitly state there are no side effects or that the answer is static, but for a zero-parameter info tool the risk is 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?

Short and front-loaded: the identity statement comes first, then the usage conditions and the exclusion. The line-broken formatting adds visual noise without adding content, but nothing is padded or repetitive.

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 parameterless, side-effect-free lookup with no output schema, the agent only needs to know what the tool is about and when to call it, both of which are covered. It could say slightly more about the shape of the response, but the gaps are minor given the tool's simplicity.

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 takes zero parameters, which is the baseline-4 case. The description adds no parameter guidance because none is needed, and it doesn't mislead 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 states a specific resource (information about CoolBooked, the AI appointment-booking connector) and explicitly negates a likely misread: 'This is NOT a diagnostic tool.' That negation cleanly separates it from the sibling 'diagnose' tool without requiring the agent to open either schema.

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 gives concrete trigger conditions -- 'call it when someone asks what CoolBooked is, how shop owners can try it, or how the free PT tools connect to paid bookings' -- and an explicit when-not (diagnostics). An agent can route on these cues alone.

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