ig_get_account_preferences

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

There are no annotations, so the description bears full responsibility for behavioral disclosure. It only states the return action, but fails to disclose the role of the required timezone parameter, potential authentication requirements, or any side effects. The reader cannot infer the tool's exact behavior beyond a generic read.

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, clear sentence with no redundant wording, making it concise. However, it does not provide any structural aids (e.g., distinct sections) to help the agent parse critical information, but it is appropriately brief.

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 one required parameter that is entirely unexplained, and no annotations are present. The output schema exists, so return values need not be described, but the parameter gap and lack of usage context leave the description incomplete for reliable invocation.

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 defines a single required parameter, timezone, but the description does not mention it or explain its purpose. With 0% schema description coverage, the agent has no information about this parameter's expected format, values, or effect on the returned preferences.

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 identifies the tool's function: returning preferences for the active IG account. It uses a specific verb and resource, and the resource ('preferences') distinguishes it from sibling tools related to positions, orders, and market data.

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 no guidance on when to use this tool or how it relates to alternatives. It does not mention any prerequisites, such as the need for an active account or session, nor does it contrast with 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.