get_symbol_info

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

No annotations exist, so the description must carry disclosure. 'Get' implies read-only, but it does not explicitly state no side effects, idempotency, or error conditions. The description is minimal beyond the action.

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?

Single sentence, no redundant words. Information is front-loaded with the verb and resource, and the parenthetical list efficiently communicates output content.

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?

For a low-complexity tool with one parameter and no output schema, the description adequately explains what the tool returns by listing fields. No additional context is needed for an agent to understand the function.

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 only references the parameter by name. It does not specify symbol format (e.g., ticker, exchange prefix) or constraints, leaving ambiguity for the agent.

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 full symbol specification and lists the specific fields (point, digits, contract size, spread, limits). It distinguishes from siblings like get_rates and get_tick by focusing on detailed symbol metadata.

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 when to use (need symbol details) but provides no explicit when-to-use vs alternatives or exclusions. While adequate for a simple tool, it lacks guidance on context like prerequisite symbol info.

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