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

Annotations already cover readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is clear. The description adds useful behavioral context by stating that the result is a 'frozen' reason code and includes the rule-set version, source page, and decision_id, which clarifies that this is a deterministic decision output rather than a live enforcement action.

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 dense sentence that front-loads the core decision and then lists inputs and outputs without wasted words. Every clause contributes either to what the tool does or what it returns.

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?

The tool has 6 parameters, 4 required, no schema descriptions, and an output schema. The description covers the overall purpose and return fields, but it leaves several parameter semantics unexplained and offers no usage context. Given the complexity and missing schema coverage, more detail is needed for an agent to invoke this correctly in all cases.

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 schema description coverage at 0%, the description must compensate, and it does partially: it enumerates pathway values and specifies substance identifier formats (name, INN, or unii:). However, actor_class, channel, ship_to, and credential are left undefined, and credential is not mentioned at all, so the compensation is incomplete.

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 decision outcome — allow, deny, or require_rx — and names the relevant input dimensions (substance, pathway, actor class, channel, ship-to). It also distinguishes itself from siblings by noting the frozen reason code, rule-set version, source page, and decision_id produced for downstream tools.

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 explicit guidance about when to use this tool versus alternatives such as get_compounding_eligibility, get_pathway_status, or create_order_intent. The phrase 'for the downstream tools' implies a pipeline position, but it does not state conditions, exclusions, or selection criteria.

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