get_token_info

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

No annotations are provided, so the description carries full burden. It states the HTTP method (GET), the specific endpoint, and the return structure with fields like merchant_id, scopes, expires_at. It implies a read-only operation without side effects, which is appropriate. Could be improved by explicitly stating there are no modifications or rate 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?

The description is well-structured with sections for purpose, usage, API call, and return. Each sentence adds value, though it could be slightly more concise. The use of line breaks and Chinese formatting is clear but not minimal.

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?

Given the absence of output schema and annotations, the description provides a complete picture: what the tool does, when to use it, the exact API endpoint, and the structure of the return value. The agent has sufficient information to invoke the tool correctly.

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 has zero parameters (100% coverage), so the description does not need to add parameter semantics. It correctly indicates no parameters are needed and instead focuses on the return value, which adds value beyond the schema.

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 explicitly states the tool retrieves current API token info and authorization scope, including merchant, scopes, and expiry. This is a specific verb-resource pair that clearly distinguishes it from sibling tools which focus on products, orders, customers, etc.

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 description includes a dedicated '用途' section explaining it is suitable for troubleshooting API access issues and confirming token permissions. While it does not explicitly mention when not to use or name alternatives, the context is clear given the absence of other token-related tools among siblings.

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