bybit_instruments_info

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states 'Get' indicating a read operation, but fails to disclose any traits such as auth requirements, rate limits, or whether the data is live or cached. No behavioral context beyond the basic verb.

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 one sentence, which is concise. However, it lacks structure—no front-loading of key details, no separation of purpose from parameters. While not verbose, it fails to efficiently convey critical information.

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 5 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain return values, pagination (limit), or filtering (status, baseCoin). The agent lacks essential context to use the tool effectively.

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%, so the description must compensate. It adds minimal meaning by mentioning 'category' (required) and 'symbol' (optional), but ignores limit, status, and baseCoin entirely. The agent gains no insight into the purpose or constraints of these parameters.

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 verb 'Get', the resource 'Bybit instrument metadata', and the scope 'for a category and optional symbol'. It effectively distinguishes itself from sibling tools like bybit_kline and bybit_active_orders by specifying a different resource type.

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 explicit guidance on when to use this tool versus alternatives. It does not mention what category or symbol mean, nor does it exclude any cases. Sibling tools are not referenced, leaving the agent to infer usage from the name alone.

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