Accounts Get Net Worth Breakdown

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint as false. The description adds no additional behavioral context, but does not contradict annotations. With annotations present, the bar is lower; however, the description does not provide extra useful behavioral details.

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?

At 4 words, the description is extremely minimal but fails to provide necessary information. It is under-specified for a tool with 6 parameters and no output schema, making it inefficient rather than concise.

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 description is too brief to be complete. Given the tool's complexity (6 parameters, no output schema), it does not explain what the net worth breakdown contains, how filters work, or what output format to expect. The description leaves the agent with significant uncertainty.

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 description coverage is only 33% (2 out of 6 parameters have descriptions). The description 'Get net worth breakdown' adds no meaning to parameters like filters, start_date, timeframe, or session_path. With low coverage, the description must compensate, but it does not.

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 'Get net worth breakdown' clearly identifies the action (get) and resource (net worth breakdown), but lacks specificity about what the breakdown includes. It does not distinguish it from the sibling tool 'accounts_get_net_worth_performance'.

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?

No guidance is provided on when to use this tool versus alternatives like accounts_get_net_worth_performance or other tools. There is no context on prerequisites or typical use cases.

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