estimate_hook_state_cost

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

No annotations provided, so description must disclose behavior. It states computation is offline, returns per-entry capacity, reserve units, overflow warnings, and minimum scale. It does not mention if any network calls are made, but 'offline' implies local computation. Good but could explicitly note no side effects.

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?

Four sentences with no waste. First sentence states purpose, second and third explain outputs, fourth gives implementation tip. Front-loaded and easy to parse.

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?

Describes return values (capacity, units, warnings, min scale) adequately without output schema. However, lacks explicit return structure (e.g., object fields), but enough for an AI to infer usage. Sibling tools provide contrast.

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?

Description adds meaning for all 3 parameters: explains 'scale' range (1–16), 'entries' as objects with valueBytes (size in bytes), and 'ownerReserveIncrementXah' for optional XAH conversion. This goes beyond the schema, which only describes one parameter.

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?

Description clearly states it computes owner-reserve cost of Hook State entries under ExtendedHookState, using specific verb 'Compute' and resource 'owner-reserve cost'. It distinguishes from sibling tools like 'estimate_hook_fee' by focusing on state entries.

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?

Provides clear guidance on when to use: given value size and scale, returns cost info. Also specifies optional parameter to get XAH figure. However, no explicit when-not-to-use or alternatives are mentioned beyond the tool's scope.

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