okx_get_profit_sharing_details

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

Annotations are absent, and description only indicates a read operation via '[L:READ]', lacking details on authentication, side effects, or any behavioral constraints beyond that.

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 very short, but the concise format sacrifices clarity; the structure (tag + prerequisite) is minimal yet incomplete for effective use.

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?

Despite having many sibling copy trading tools and no output schema, the description fails to explain what the tool returns, how to interpret results, or how it fits into the broader workflow beyond calling agent_catalog.

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% with both parameters ('limit' and 'instType') having clear descriptions; the tool's description adds no extra meaning beyond the schema, meeting the baseline.

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 uses cryptic tags like '[L:READ]' and 'CAT:[策略-跟单]' without explaining the tool's core function; relies on the name 'get_profit_sharing_details' to imply purpose, but the description itself is vague.

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?

Only provides a prerequisite call '→ 请先调用 agent_catalog' without specifying when to use this tool over siblings like okx_get_profit_sharing_total or other copy trading tools.

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