getBizTokenDetails

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

No annotations provided, so description carries full burden. It discloses return content, risk flags, status, and the showMessage notification behavior. However, it does not explicitly state read-only nature or lack of side effects, but as a query tool this is implicit.

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?

Description is verbose and contains repetitive information, especially in the 'Agent hint' block which largely duplicates the main paragraph. Important info is front-loaded, but redundancy reduces conciseness.

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 no output schema, description covers return fields, notification behavior, and prerequisites. Missing explicit error handling or authentication notes, but for a read-only query tool the coverage is adequate.

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 0%; description adds value by telling agents to get chainCode and tokenAddress from specific list responses. However, it mentions a showMessage parameter not in the schema, causing confusion. No format or constraint details added beyond source guidance.

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 tool queries detailed on-chain token information, listing specific return fields. It distinguishes from siblings by explicitly directing to getBizTokenPriceList for prices and getBizTokenList for browsing.

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?

Explicitly says to call when user asks about token details, project info, or risk status. Provides prerequisite parameters from getBizTokenList or getAssetList. Clearly states what not to use for (prices, browsing) and gives alternative tool names.

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