bitget_methods

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

With no annotations provided, the description must carry behavioral disclosure. It states that the tool returns a complete method inventory with descriptions and usage instructions, which outlines output content. However, it does not discuss output format, limitations, or explicitly confirm read-only behavior, though 'Get' suggests it.

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 consists of two sentences, front-loaded with the core action and concise in wording. No unnecessary details or repetition are present, with each sentence contributing to the understanding of the tool's purpose and output.

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 simple, parameterless tool with no annotations or output schema, the description sufficiently explains what the user will receive: a complete method list with descriptions and usage instructions. It provides enough context for typical use, though it could be slightly more explicit about the relationship to 'bitget_method_detail'.

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 tool has zero parameters, so the input schema trivially covers all semantics. The baseline for 0 params is 4, and the description adds no conflicting or redundant parameter information, implicitly indicating no inputs are required.

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 retrieves all API method lists and related documentation for the Bitget Exchange SDK, using the specific verb 'Get' and identifying the resource. It distinguishes itself from sibling 'bitget_method_detail' by emphasizing the complete inventory, whereas the detail tool likely focuses on a single method.

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 implies usage for developers needing an overview of available functional interfaces, but it does not explicitly mention when to use this tool versus 'bitget_method_detail' or other exchange method listers. No exclusions or alternatives are named, leaving the choice somewhat implicit.

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