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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description's one genuine contribution is "Starts no call", a meaningful side-effect boundary in a domain full of call-triggering operations; it says nothing about permissions, data volume, or pagination on a large directory.

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?

A single run-on sentence that duplicates the title verbatim, listing a dozen fields in one undifferentiated stream. The most behaviorally important clause, "Starts no call", is buried at the very end rather than front-loaded.

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?

With no output schema, the field enumeration does real work by describing the returned record shape, including removed pharmacies and change history. However, it omits any explanation of the required scope parameters or the read's size/pagination characteristics, leaving gaps for a directory that could be large.

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% and the description never mentions the two required parameters (company UUID, environment enum). The names and formats are largely self-explanatory, but the agent gets no statement of what company/environment scope the read to or whether production vs staging directories differ.

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 ("Read the pharmacy directory") and enumerates the data returned, which separates it from the sibling writers summer_pharmacy_calls_directory_update and summer_pharmacy_calls_address_update. It never names those siblings directly, so the differentiation is implied rather than explicit.

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?

There is no when-to-use/when-not guidance and no reference to an alternative tool. "Starts no call" hints that this is the safe inspection step before call-related actions, but the agent must infer that; nothing states the condition for choosing this over directory_update or the settings readers.

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