Check smart copy parameters

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the required 'Bot reading' permission scope, the weight value, and the concrete outputs (max investment, max leverage, notional/available limits).

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?

Front-loaded with the action, then permission requirement, then return values, in a few tight sentences. No filler, and the most decision-relevant facts (purpose, permission, what comes back) appear first.

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?

With no output schema, the description usefully enumerates what is returned, and it discloses the permission prerequisite. It is complete enough to invoke correctly; only the relationship to the create tool is left implicit.

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 description coverage is 100%, so every parameter (base, quote, leverage, signal_type, signal_param, quote_investment) is already documented in the schema. The description references the 'base/quote/signal combination' only in passing and adds no format, range, or validation detail beyond the schema — baseline 3.

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?

States a specific verb (validate/check) and resource (smart copy bot creation parameters, max investment limit), and the word 'smart copy' cleanly separates it from the futures/spot grid param-check siblings. It stops short of naming the create_smart_copy_order sibling it gates, so it is clear but not fully differentiated.

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?

Usage is only implied: an agent infers this is a pre-flight validation step before pionex_bot_create_smart_copy_order. There is no explicit 'use before creating' statement, no when-not, and no pointer to the sibling that consumes the validated parameters.

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