tv_symbol_search

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

The annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds that results are exchange-qualified tickers with descriptions/types, but it does not disclose rate limits, pagination behavior, or any other operational traits beyond what annotations and the output schema would imply.

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?

Two short sentences with no filler. The action and resource are front-loaded, and the return contents fit in a compact clause, making the definition easy to scan and act on.

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 simple read-only symbol search with an output schema and clear annotations, the description is largely sufficient. It could mention when to prefer this over tv_screener_run, but the core invocation context is adequately covered.

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 schema fully documents the 'text' parameter with examples, leaving 'limit' without a semantic description. The tool description itself does not compensate by explaining limit or its role in result size, although the parameter name and min/max/default constraints make its meaning fairly inferable.

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 uses a specific verb and resource: 'Search TradingView's symbol directory.' It also states the output shape ('exchange-qualified tickers with descriptions and types'), which clearly differentiates it from the screened runs, TA summaries, and data bar tools listed as siblings.

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 makes the intended use clear: an agent should call this when a user wants to find symbols in TradingView's directory. It does not explicitly name alternatives or exclusions, but the verb and resource are specific enough to disambiguate from the sibling tools.

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