BinancePortfolioMarginFundAutoCollection

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

There are no annotations, so the description must carry the full behavioral burden. It implies a configuration mutation but does not describe permissions, side effects, what exactly is enabled/disabled, whether the setting is account-wide, or what the response contains.

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 definition is a single clear sentence with no wasted wording, and the action is front-loaded. It is appropriately sized for a concise tool description, even though more behavioral detail would be useful elsewhere.

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 portfolio-margin configuration mutation with no annotations and no output schema, the description is too sparse. It omits prerequisites, the effect of enabling/configured auto-collection, and what an agent should expect after invocation.

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%, and the single recvWindow parameter is documented in the schema as an upper-bounded number. The description adds no parameter-specific meaning beyond the schema, which is acceptable given complete schema coverage.

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 and resource: enabling or configuring fund auto-collection on a portfolio margin account. It distinguishes this from the sibling fund collection tool by saying 'auto-collection,' though it does not explicitly name the alternative.

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 explicit guidance is given for when to use this tool versus portfolio margin fund collection, auto-repay settings, or other account configuration tools. The only implied context is that it applies to portfolio margin accounts.

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