get_screener

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

The description does not disclose behavioral traits beyond what annotations already provide. It does not mention that sorting is client-side, that pagination is 1-based, or that maxPages controls the number of API calls. With readOnlyHint=true already indicating a read-only operation, the description adds minimal value for behavior.

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, which is concise and front-loaded. However, it omits important details that could be included without much length, such as pagination or client-side sort behavior. It is not wasteful, but not optimally informative.

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 complexity of the tool (9 optional parameters, client-side sort, pagination, and aggregation via maxPages), the description is too brief. It does not mention the presets for fields, the client-side nature of sorting, or the aggregation behavior. An output schema exists but is not shown; the description should compensate by explaining the result structure. It falls short.

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%, so the schema already documents all parameters. The description adds a high-level summary of filtering and sorting, but does not provide additional meaning beyond what the schema offers. For example, it doesn't explain the difference between presets and comma-separated fields. Baseline score of 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 action ('Get') and resource ('cryptocurrency screener results'). It mentions filtering and sorting capabilities, making the tool's purpose understandable. However, it does not explicitly distinguish it from sibling tools, but since no other tool retrieves screener results, this is acceptable.

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?

No guidance is provided on when to use this tool versus its siblings. The description does not mention typical use cases, prerequisites, or when to avoid using it. An agent would have to infer usage from the name and parameters alone.

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