tickory_get_market_data

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

The description implies a read operation via 'Get', but without annotations, it does not confirm read-only nature, rate limits, or auth needs. It adds minimal behavioral context beyond the 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?

Single sentence with no wasted words. Front-loads the key action and resource.

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?

With an output schema present, return format explanation is unnecessary. However, the description lacks context on data source (exchange), latency, or prerequisites. Adequate for a simple tool but not fully complete.

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 description adds 'one or more' clarifying that the array parameter can accept multiple symbols. The schema's items description provides symbol examples, so the description complements but doesn't fully compensate for low schema coverage.

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 live price, indicators, and metadata for symbols. The verb 'Get' and resource 'market data' are specific, and it distinguishes from siblings like tickory_describe_indicators or tickory_list_symbols by focusing on live data retrieval.

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 on when to use this tool versus alternatives. Siblings exist for describing indicators or listing symbols, but the description does not explicitly state that this is for live market data or that other tools cover different aspects.

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