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

With no annotations, the description carries the burden of behavioral disclosure. It describes the return as 'all healthcare and administrative services' and gives examples, which adds useful context. It does not explicitly state that it is a read-only operation or address potential errors, but the tool name and verb imply a safe read.

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 concise and well-structured: a one-line purpose, a brief return explanation, and a clean Args section. Each sentence adds relevant information without redundancy or fluff.

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 tool with a single parameter and an output schema, the description adequately communicates what the tool does and what to expect. It provides example service categories and instructs how to obtain the required ID. Edge cases like invalid IDs are not covered but are not essential for this simple retrieval tool.

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 provides no description for facility_id, so the description's explanation that it is a VA facility ID with an example ('vha_648') and source instruction from find_va_facilities fully compensates. This adds significant meaning beyond the bare schema type.

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 'get_facility_services' retrieves the list of services for a specific VA facility, using a specific verb and resource. It distinguishes itself from sibling tools like find_va_facilities and get_facility_detail by focusing explicitly on 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?

The description provides clear context for when to use the tool (when you have a facility and need its services) and instructs on obtaining the facility_id from find_va_facilities. However, it does not explicitly mention when not to use it or compare it with get_facility_detail, so it lacks an explicit exclusion statement.

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