Get Limits

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

Annotations already indicate read-only, non-destructive, and idempotent behavior. The description adds valuable behavioral details: it's a start-of-day snapshot in a single T365 slice, not intraday, and hides zero rows by default. This goes beyond annotations by clarifying the temporal and filtering behavior.

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 concise at two sentences, front-loading the main purpose and key behavioral notes. Every sentence adds useful information without redundancy or unnecessary detail.

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 (money limits, securities, futures) and lack of output schema, the description covers the main elements (freeByCurrency, loadDate) and flags important behaviors (zero rows, snapshot nature). It allows an agent to understand the scope and data limitations, though it doesn't detail output structure.

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 coverage is 100%, so parameters are well-documented in the schema. The description adds value by explaining the includeZero parameter's effect (hiding zero rows), which aligns with the schema description. However, it does not add new meaning beyond what the schema provides for outputPath and outputFormat.

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 account limits including money limits, securities, and futures. It differentiates from sibling tools like get_portfolio by specifying the exact types of limits. The verb 'get' implies retrieval, and the resource 'limits' is explicit. However, it doesn't explicitly contrast with siblings for usage.

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 notes that the API returns a start-of-day snapshot (not intraday) and that zero rows are hidden unless includeZero=true. This provides context but does not give explicit guidance on when to use this tool versus alternatives like get_portfolio. It implies usage for limit inquiries but lacks when-not-to-use or alternative suggestions.

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