bridge_get_quota_and_fee

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

With no annotations, the description carries full responsibility for behavioral disclosure. While 'get' implies a read-only operation, it does not state side effects, permissions, rate limits, or return format. The reference to 'section 1.2.3' is opaque and adds no behavioral context.

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 a single sentence, front-loaded with the core purpose. However, the trailing '(section 1.2.3)' is not actionable for an AI agent and slightly detracts from usefulness, preventing a perfect score.

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?

The description gives a basic sense of what is returned (quota and fees) but lacks details on the response structure or any contextual relationship to other bridge tools. Since there is no output schema, more explanation of the result would be beneficial. The complete schema coverage for parameters helps, but the overall context is still thin.

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 schema covers all parameters with descriptions (100% coverage), so the baseline is 3. The description adds no additional semantics about parameters, merely restating that the tool returns quota and fees. It does not clarify the optional tokenPairID's role 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 bridge quota (min/max limits) and fees in a single call. It clearly distinguishes this from sibling tools like bridge_get_token_pairs or bridge_check_status, which serve different purposes, making the intent unambiguous.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention prerequisites (e.g., needing token pairs first), nor does it indicate that this should be called before creating a bridge transaction. The 'in one call' hint implies efficiency but is not explicit advice.

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