Get Max Buy/Sell Size

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

With no annotations, the description discloses a key behavioral requirement: authentication via POLONIEX_API_KEY and POLONIEX_API_SECRET. The word 'Fetch' implies a read operation, but it does not explicitly describe the safety profile or output structure, leaving some gaps.

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, with the core action first and the auth requirement second. No redundant phrases or filler.

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 tool with one parameter, no output schema, and no annotations, the description covers the purpose, the margin context, and authentication requirements. It doesn't explain the response format, but for this simple tool the information is sufficient.

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 input schema offers 100% coverage with an example ('BTC_USDT') for the single 'symbol' parameter. The description's mention of 'a symbol' adds no additional semantic value beyond the schema, so the baseline score 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 states a specific action: 'Fetch the maximum and available buy/sell amounts for a symbol on margin.' This clearly distinguishes it from sibling get_* tools by focusing on margin-specific size limits. The verb 'fetch' and resource 'buy/sell amounts' are well-defined.

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 phrase 'on margin' provides clear context for when this tool is appropriate, distinguishing it from other quote tools. However, it does not explicitly name alternative tools for when margin is not involved or state when not to use it.

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