accountFixedBorrow

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

No annotations are provided, so the description must disclose all behavioral traits. It mentions that this creates a real loan with interest obligations, depends on available supply, and is for Unified account only. However, it does not explain side effects (e.g., what happens on insufficient supply), authorization needs, 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 bullet points for rules and a separate agent hint. It is concise but includes necessary details. Every sentence adds value, though a bit more brevity could be achieved.

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 tool's complexity (6 parameters, no output schema, no annotations), the description provides basic context like account type and dependencies but lacks information on return values, error handling, and prerequisites like collateral requirements.

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 description coverage is 0%, so the description is expected to explain parameters. It partly does: it explains the 'term' (enum values), 'strategyType' (PARTIAL/FULL), and 'repayType' (1/2). But it does not explain 'orderCurrency', 'orderAmount', or 'annualRate', leaving gaps.

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 verb 'Create' and the resource 'fixed-rate borrow order for Unified account'. It includes specific rules and constraints (e.g., supported terms, strategy types) that distinguish it from other tools. The title itself is specific.

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 rules for when to use the tool (e.g., fixed terms, order strategy, maturity handling) and an agent hint that requires user confirmation before execution, indicating when not to proceed automatically. However, it does not explicitly compare this tool to other borrow-related siblings.

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