lookup_ticker_cik

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

With no annotations, the description carries full burden and does so well. It discloses that the tool bypasses and can clear the session-level failed-ticker blacklist, explains cache-first behavior via refresh=false, and notes alias retry behavior—all critical operational traits beyond the schema.

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 longer than minimal but well-structured with a one-line summary, strategy, critical rules, and an example. Every section adds actionable value and the critical rules are front-loaded after the summary, making it easy for an agent to parse.

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?

The description covers trigger conditions, recovery workflow, cache/refresh policy, side effects, and alias retry. Since an output schema exists, it does not need to explain return values, and the included operational guidance makes it complete for this diagnostic tool.

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 0%, but the description fully compensates. It explains 'ticker' with the example 'BABA' and clarifies 'refresh' as 'Force re-download of company_tickers.json from SEC (default: false)', adding practical meaning beyond the bare schema fields.

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 opens with a specific verb+resource: 'Look up the SEC CIK mapping for a ticker symbol.' It also labels the tool as a 'Diagnostic / recovery tool,' clearly distinguishing it from siblings like download_sec_report or list_sec_filings.

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 <strategy> section states exactly when to invoke: ONLY when download_sec_report or list_sec_filings returns 'CIK not found' or 'Ticker not found', and explicitly says not to use it as a routine first step. It also provides post-lookup retry guidance and alias handling.

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