Get Scanner Parameters

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

Annotations already declare readOnly=true. The description adds meaningful behavioral context: caching for 15 minutes and auto-acquisition/release of brokerage session. This helps the agent understand staleness and session handling, adding value beyond annotations.

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, 20 words, first sentence states purpose, second adds key behavioral details. No wasted words.

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 no-param read-only tool, the description provides caching and session context. It could benefit from a brief note about the return value shape, but the tool is simple enough that this is a minor gap.

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?

With zero parameters, schema coverage is vacuously 100%, and the baseline for 0 params is 4. The description doesn't need to explain parameter syntax; it focuses on the tool's purpose.

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 resource ('market scanner parameters') and the action ('get'), making the purpose unambiguous. It doesn't explicitly distinguish from sibling run_scanner, but the resource is specific enough.

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 on when to use this vs alternatives. The 'Requires brokerage session' note is a prerequisite, not a when-to-use instruction. It doesn't mention run_scanner or that this should be called to discover available scanner parameters before running a scan.

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