binance_get_api_restrictions

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

Annotations already mark this as read-only, idempotent, and non-destructive, and the description adds meaningful context: the endpoint is SIGNED with IP weight 1, risky flags are marked with ⚠️, and error -2015 maps to missing Reading permission or non-allowlisted IP. No contradiction with annotations.

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 short headed sections: core behavior, when to use, when not to use, returns, examples, and error handling. Every section adds actionable information without redundancy.

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?

It covers the endpoint, authentication context, return format, error handling, usage boundaries, and an example call. For a tool with a single optional parameter, an agent has everything needed to select and invoke it 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 only meaningful parameter, response_format, is already described in the schema, and the description reinforces it with 'raw JSON with response_format="json"' and an example params = {}. Schema coverage is listed as 0%, but the description compensates well for the one user-controlled parameter.

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 opens with a specific verb and object: 'Report the full permission flag set on the configured API key.' It also names the exact Binance endpoint and explicitly contrasts itself with binance_health_check, so an agent can distinguish this from sibling tools.

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 provides explicit 'When to Use' and 'When NOT to Use' sections. It names binance_health_check as the alternative for quick post-startup checks and explains that the sibling already calls this endpoint as part of a broader check.

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