get_account_hooks

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

The description mentions 'Read-only', which indicates no destructive side effects, but with no annotations provided, this is minimal transparency. It also notes the decoding of the HookOn bitmap, adding some behavioral context beyond the schema.

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, relatively clear sentence with no extraneous information. It is efficient but could be improved by front-loading the verb.

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?

With two parameters and no output schema or annotations, the description provides a basic idea of the output but lacks details on required fields, defaults, or the return format. It is adequate but has gaps.

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%, and the description does not elaborate on the parameters 'address' or 'network'. It only implies the address via 'account', adding little value beyond the schema.

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 hooks installed on an account with decoded HookOn bitmaps, which distinguishes it from sibling tools like get_hook_definition or get_hook_state. However, the phrasing is somewhat passive and could be more active (e.g., 'Retrieve').

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?

No guidance is provided on when to use this tool versus alternatives such as get_hook_definition or get_hook_state. The description lacks explicit usage context or exclusion criteria.

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