get_account_config

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

No annotations are provided, so the description carries the behavioral disclosure burden. It explicitly conveys a read-only operation ('Retrieves') and indicates the current state of the configuration, adding context beyond the tool name. While it does not discuss error conditions or permissions, the zero-parameter, read-only nature makes this adequate, though slightly more detail on response traits could push it higher.

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, well-structured sentence that leads with the action and includes a concise list of the settings covered. There is no filler or redundant information.

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 tool has zero parameters and includes an output schema for response details, so the description's job is simply to state what the tool does and what it covers. The sentence fully achieves this, making the description complete for this simple read-only tool.

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?

This tool has zero parameters, so the baseline is 4 per the rubric. The description cannot add parameter-specific meaning because there are none; the description's enumeration of output contents is the relevant semantic contribution.

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 uses the specific verb 'Retrieves' and clearly identifies the resource as 'account configuration settings', while enumerating key settings (trading restrictions, margin, PDT checks, options level). This differentiates it from siblings like get_account_info and update_account_config.

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 clearly implies when to use this tool: whenever the agent needs the account's configuration settings, such as margin or PDT status. It does not explicitly mention alternatives or exclusion criteria, but the specificity of the listed settings provides enough contextual guidance to distinguish it from other account-related tools.

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