broker_sync_connections

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

With no annotations, the description carries the full behavioral burden, yet it only implies read-only via the verb "List." It says nothing about authentication requirements, pagination/result size, rate limits, or what "normalized" entails, all of which matter for a broker-integration 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 content is short, but the description literally duplicates itself: the bracketed tag line and the trailing sentence are the same text repeated verbatim. That is pure redundancy rather than front-loaded structure.

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?

For a one-parameter, read-only list tool with no output schema and no annotations, the description covers the essential "what" adequately. It is minimally sufficient, but omits return shape, pagination, and the meaning of "normalized," which the agent would need for correct interpretation.

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% for the single user_id parameter, so the schema does the documentation work and the baseline of 3 applies. The description's phrase "a user's" lightly reinforces that user_id scopes the result but adds no format or constraint detail beyond the schema.

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 states a specific verb+resource ("List a user's connected brokerage accounts") and the "(normalized)" qualifier hints at the data shape. It is clear what the tool does and implicitly distinct from siblings like broker_sync_positions or broker_sync_balances, though it never explicitly names those alternatives.

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?

There is no when-to-use guidance, no prerequisites, and no mention of the sibling tools it might be confused with (positions, balances, transactions, register_user). The agent must infer selection from the name alone.

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