symbology_resolve

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

The description indicates the tool operates 'across a date range', implying historical resolution. However, it does not disclose whether the operation is read-only, error handling, or other important behaviors. Since no annotations are provided, the description carries the full burden but only partially addresses it.

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 sentence with no extraneous information. While it is concise, it could be slightly expanded to include more critical details without being verbose. It is well-structured and front-loaded.

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 complexity (6 parameters, 5 required) and the absence of an output schema, the description should explain the return format or provide more behavioral context. It does not mention what the output looks like, leaving a significant gap for the agent to infer.

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 coverage is 100% with descriptions for all parameters. The description adds marginal value (e.g., 'across a date range' reinforces start_date/end_date usage) but does not provide significant additional meaning beyond the schema. Baseline 3 is appropriate.

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 action (resolve) and what it acts upon (symbols to instrument IDs or other symbol types) across a date range. It uniquely identifies the tool's function among siblings, as no other tool in the list appears to perform symbol resolution.

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. The description does not mention prerequisites, limitations, or situations where another sibling tool might be more appropriate.

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