hl_approve

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

Annotations show readOnlyHint=false and openWorldHint=true. The description adds details: it requires signing, is one-time, revocable, and has a minimal 0.001% max fee. This provides behavioral context beyond annotations, though no mention of failure modes or state changes.

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 two sentences with no wasted words. It front-loads the main action and includes key constraints (one-time, revocable, fee percentage).

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 no parameters, no output schema, and low complexity, the description covers all essential aspects: purpose, one-time nature, revocation, and fee. No gaps remain for an agent to use the tool 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 tool has zero parameters with 100% schema coverage. The description adds no parameter info, which is acceptable as there are none. Baseline of 4 applies since no compensation is needed.

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 retrieves a one-time approveBuilderFee action for signing with a MAIN wallet to authorize SwapTitan as a builder. It uses a specific verb (approve, get action) and resource (builder fee), distinguishing it from siblings like hl_build_order.

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 indicates the action is one-time and revocable, implying when to use (for initial authorization). However, it does not explicitly mention prerequisites or alternatives, leaving moderate clarity for usage decisions.

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