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

The readOnlyHint annotation already tells the agent this is a safe read operation. The description adds useful context about the content (e.g., the one-appointment-per-day rule), but it doesn't disclose other behavioral details like response format or whether information is dynamic. It doesn't contradict annotations.

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, compact sentence that front-loads the subject and lists key information. It is efficient, though the list format could be slightly clearer with separators or a more structured layout.

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 0-param read-only tool with no output schema, the description adequately covers what the agent can expect in the response. It includes specific details like the one-appointment rule and booking instructions, making it suitably complete for its simple scope.

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?

With zero parameters in the schema, the baseline is 4. The description adds meaning by explaining what the tool returns, but since there are no params, there is nothing more to elaborate. It appropriately doesn't invent parameter details.

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 tool's purpose: providing info about the vertebrologist, listing specific content areas (specialty, treats, address, slot length, rules, booking). This distinguishes it from sibling tools like book or get_availability, which are action-oriented or availability-focused.

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 context is clear: this tool is for static doctor information, not for actions like booking or cancellation. However, it doesn't explicitly name alternatives or say when not to use it, so it falls short of full explicit guidance.

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