get_symbol_info

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

The description acknowledges the read-only nature (consistent with readOnlyHint) and adds that errors occur for unresolvable tickers. It lists all returned fields, providing transparency beyond the annotations alone.

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 concise and well-structured: a clear opening sentence followed by a bulleted list of returned fields. Every sentence adds value, and there is no redundancy.

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 the tool's simplicity (one parameter, has output schema), the description is fully complete. It covers the single parameter, lists all return fields, and notes an error condition. No gaps remain.

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?

With 100% schema coverage, the input schema already describes the parameter. The description adds only examples (e.g., 'TLV') but does not provide extra semantic value beyond what the schema offers.

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's function: 'Resolve one BVB ticker to its symbol metadata.' It specifies the action (resolve) and resource (ticker metadata), and is distinct from sibling tools like search_symbol (searching) and get_candles (candles).

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 implies usage when a specific BVB ticker is known and metadata is needed, but does not explicitly state when to use or not use this tool versus alternatives. No exclusions or when-not-to guidance is provided.

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