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

No annotations are provided, so the description carries the behavioral burden. It discloses that a supplied age yields a fuller breakdown including percentiles and homeowner/renter splits, but it omits data source, time frame, and other limitations.

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 main purpose is front-loaded and the parameter behavior is clearly separated. The docstring-style Args block is slightly awkward but not wasteful.

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 simple one-parameter statistical lookup with no output schema, the description gives a reasonable picture of the returned metrics and breakdown. It remains incomplete on data provenance, units, and valid age input ranges, which matter 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 0%, but the description compensates well for the single optional age parameter by explaining that supplying it returns that age group's detailed breakdown and omitting it returns every age group. It still lacks valid age ranges or units.

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?

States a specific resource and metrics: median, average and top-percentile net worth for US families by age. It does not explicitly distinguish itself from the sibling net_worth_percentile, so it is clear but not fully differentiated.

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?

Explains that age is optional and what changes when it is provided versus omitted, which implies usage. However, it does not say when to choose this tool over net_worth_percentile or other siblings.

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