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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds behavioral context beyond that: the tool is coupled to gate_transaction output and only accepts allow or require_rx decision types, which is not derivable from the schema or annotations.

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?

Two short sentences with no filler; the core purpose is front-loaded and the key precondition follows immediately. The phrasing is slightly fragmentary ('Licensed parties for...') but economical and every clause earns its place.

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?

An output schema exists so return values need no explanation, and annotations cover the safety traits. The description states the gate_transaction dependency, which is the main integration requirement. It omits guidance on non-eligible decisions and tenant semantics, leaving minor gaps for a moderate-complexity 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?

With 0% schema description coverage, the description must carry parameter meaning. It meaningfully explains decision_id (must come from gate_transaction and be allow/require_rx) and clarifies presentation and jurisdiction as the look-up keys. However, tenant is only mentioned ('tenant as a parameter') without explaining its role, and no format constraints are provided.

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 the resource ('licensed parties') and scope ('for a presentation in a jurisdiction'), and anchors it in the pipeline by requiring a decision_id from gate_transaction. It is distinguishable from siblings like resolve_actor and search_cleared_items, though the noun-phrase opening is slightly less explicit than a verb-led statement.

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?

It conveys the key precondition—only usable with an allow or require_rx decision_id from gate_transaction—which orients the agent to the correct point in the flow. It does not name alternative tools or explicitly state when not to use it (e.g., for deny decisions), leaving exclusions to inference.

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