search_screener_columns

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

No annotations provided, so description carries full burden. Describes basic behavior: search by keyword, returns column IDs that are case-sensitive. Does not disclose side effects, authorization needs, or performance characteristics. Adequate for a simple search tool, but lacks depth.

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 sentences, front-loaded with purpose, immediately followed by usage context. Every sentence serves a purpose: first defines the action, second explains why and how to use it. No redundant information.

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 only one parameter, output schema exists, and no annotations, the description is complete. It explains the tool's role (discovery before `query_screener`), parameter usage with examples, and the return behavior (case-sensitive IDs). No gaps for this complexity level.

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?

Input schema has 100% coverage for `query` parameter. Description adds value by providing concrete examples ('dividend', 'revenue', 'RSI', etc.), which helps the agent formulate appropriate queries. No additional constraints or formats mentioned, but examples are helpful.

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?

Clearly states 'Search for available TradingView screener indicator or metric column IDs by keyword.' Verb 'search' and resource 'column IDs' are specific. Directly distinguishes from sibling `query_screener` by stating it's for discovering column IDs before passing them.

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?

Explicitly advises using this tool before `query_screener` to discover case-sensitive column IDs. Provides context of when to use. Does not mention exclusions or alternatives, but the guidance is clear and actionable.

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