tickory_run_scan

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

No annotations exist, so the description must disclose behavioral traits. It mentions 'run immediately' but does not specify side effects (e.g., whether the scan is destructive, rate limits, or auth requirements). The return of 'matching symbols with indicator values' is stated but lacks detail on behavior 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?

The description is a single sentence of 10 words, clearly stating the action and expected outcome. Every word is necessary, with no redundancy or filler.

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 (2 params, no nested objects, output schema present), the description is adequate but lacks usage context and behavioral transparency. It does not explain what 'indicator values' are or how symbols override works, which an output schema with complete descriptions could mitigate.

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 input schema provides descriptions for both parameters (scan_id and symbols), and the description adds no new semantics beyond implying that symbols parameter is for filtering results to matching symbols. With 100% schema description coverage, 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 tool runs a scan immediately and returns matching symbols with indicator values. It uses a specific verb ('run') and resource ('scan'), and distinguishes from siblings like tickory_get_scan (retrieve without running) and tickory_run_ad_hoc_scan (run without predefined scan_id).

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 the tool is for immediate execution of a predefined scan, but does not provide explicit guidance on when to use it versus siblings like tickory_run_ad_hoc_scan or tickory_get_scan. No exclusions or prerequisites are stated.

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