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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds valuable context about the dependency on gate_transaction and the licensed-party source, which goes beyond the annotations. No contradictions exist.

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 sentence that is concise and front-loaded with the core purpose. It avoids verbosity, though the packed conditional clause could be clearer. Overall, it is appropriately sized for the tool's simplicity.

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?

While the output schema and annotations fill some gaps, the description leaves presentation_id and tenant unexplained. For an agent to correctly invoke this tool, it needs to know what presentation_id refers to and how tenant is used. The prerequisite is clear, but parameter semantics are under-specified, making the definition only partially complete.

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%, so the description must compensate. However, it only mentions decision_id implicitly and does not explain presentation_id or tenant. The parameter names are somewhat self-explanatory, but with zero schema descriptions, the tool provides minimal guidance for constructing valid calls.

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 returns 'Price basis (list · contract · reimbursement) from a licensed party' and specifies a prerequisite condition tied to gate_transaction. This distinguishes it from sibling tools like get_availability or get_item, making the purpose unmistakable.

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 explicitly says 'once gate_transaction has answered allow or require_rx (decision_id)', indicating when this tool should be used and that a prior decision is required. It doesn't list exclusions or alternatives, but the conditional context is sufficient for an agent to understand the usage scenario.

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