get_integration_info

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It correctly implies a read-only retrieval, but it does not disclose that the 'integration' parameter is optional (required: 0) or what happens when omitted. It also does not mention potential errors, rate limits, or response size. This is a notable gap for a simple but unverified behavior.

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, succinct sentence that is front-loaded with the operation and resource. Every phrase adds value: the integration list, the field names, and the parenthetical clarification. No unnecessary words or fluff.

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 there is no output schema, the description must fully specify the return contract. It lists the returned categories but omits the response format, the behavior for an omitted parameter, and any error conditions. Combined with the missing usage guidance, an agent has enough to grasp the basic purpose but not enough to confidently call it in all valid states (especially the no-argument case).

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 input schema provides only an enum with no description (coverage 0%). The description repeats the enum values and adds context about the returned fields, which helps the agent understand the parameter's purpose. However, it does not explain the optionality of the parameter or how omitting it changes the call, so compensation is partial.

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 exact verb ('Get') and resource ('details about a Horizen integration'), lists the valid integration names, and specifies the kinds of details returned (category, status, supported networks, access method, docs paths). This clearly distinguishes it from sibling get_* tools that target chains, bridges, tokens, or contract addresses.

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 provides no guidance on when to use this tool versus its siblings (get_chain_info, get_bridge_info, get_token_info, etc.). It neither states the selection criteria nor mentions exclusions. An agent would have to infer the appropriate context from sibling names alone.

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