Screener Recommend Strategies

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

Annotations already indicate readOnlyHint, idempotentHint, and destructiveHint false. The description confirms a read-only listing operation. No additional behavioral traits are disclosed beyond what annotations provide, which is adequate for this simple tool.

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 two sentences, each sentence serving a distinct purpose: stating what the tool does and how to use the result. No filler words or 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 the tool's simplicity (one parameter, output schema present, many siblings), the description is sufficient. It covers purpose and next steps. However, it could mention that the output is a list of strategy identifiers, but the output schema likely handles that.

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 100% with a single parameter. The description adds value by listing the allowed market codes and specifying the default value ('US'), which the schema only describes as a string. This helps the agent choose appropriately.

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 'List platform-preset screener strategies' which specifies the verb (list), resource (preset screener strategies), and differentiates from user-defined strategies. It also mentions market parameter options, adding specificity.

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 provides explicit guidance on how to use the output: pass the id to screener_search to run or to screener_strategy to inspect filters. It implies the tool should be used before those, but does not explicitly state when not to use it or mention alternatives like screener_user_strategies.

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