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 explains the possible outcomes (allow, deny, require_rx) and the returned fields (frozen reason code, rule-set version, source page, decision_id). It also specifies accepted formats for substance and pathway values. However, it does not state whether the tool is read-only, has side effects, or how the decision is derived, leaving some uncertainty.

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, information-dense sentence that front-loads the purpose and lists inputs and outputs without waste. It is concise yet covers the key aspects, though slightly long due to the enumeration of pathway options.

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?

Given the tool has 6 parameters, no schema descriptions, no annotations, and an output schema, the description provides a reasonable overview. It names all inputs (except credential implicitly) and states the outputs, which partially compensates for the lack of schema detail. However, it does not explain the meaning of actor_class, channel, ship_to, or credential, and does not clarify required vs optional usage beyond the schema. An agent might still be uncertain about how to populate these fields correctly.

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 has no parameter descriptions (0% coverage), so the description must compensate. It adds meaning for 'substance' (name, INN, or unii:) and 'pathway' (enumerates allowed values), but gives no semantics for 'actor_class', 'channel', 'ship_to', or 'credential'. This partial coverage is helpful but incomplete for a 6-parameter tool.

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: it gates transactions by returning allow, deny, or require_rx for a given substance, pathway, actor class, channel, and ship-to. It names specific inputs and outputs, making the action and resource clear. It does not explicitly differentiate from sibling tools, but the unique 'gate' role is evident.

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?

No explicit guidance on when to use this tool versus alternatives. It implies it is used to determine transaction authorization, but does not state conditions for use, exclusions, or mention any sibling tools. The agent must infer the context from the tool name and purpose.

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