get_markets_margin_interest

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

The description details key behaviors: default returns a compact summary, detail=True returns full data, any filter parameter triggers full data. It also mentions plan restriction (Standard+). This adds value beyond annotations, which already indicate read-only and idempotent.

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 clear sections, front-loaded purpose, and uses bullet-like format for args. It is slightly verbose in the synonym list but still concise overall.

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 and the presence of an output schema, the description covers purpose, usage, behavior, parameters, and plan limitations comprehensively. No obvious gaps remain.

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?

All five parameters are explained with format examples (e.g., 'code: Stock code (5 digits, e.g. 27800)', 'date: Date (YYYYMMDD or YYYY-MM-DD)') and behavior (detail parameter explained). This compensates for the 0% schema description coverage.

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's function: retrieving per-stock margin balance (買残・売残・貸借倍率). It also explicitly distinguishes from a sibling tool (get_markets_margin_alert) for margin restrictions, making the purpose 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?

Provides explicit guidance on when to use (for margin balances) and when not to (for restrictions, use sibling). It also explains the default behavior with no parameters vs. with parameters, aiding correct invocation.

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