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

Annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is covered. The description adds domain context that it covers private law offices and other supply counts with two periods, plus a legal disclaimer, but it does not discuss ordering, pagination, or result handling.

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 two tightly written sentences with the core data scope front-loaded. The legal disclaimer is brief and does not obscure the primary purpose.

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?

Although an output schema and rich annotations reduce the burden on the description, this is an 8-parameter analytical tool surrounded by related siblings. The description does not explain when to choose it over supply_gap or demand_trend and leaves several parameters undocumented, so an agent is not fully equipped to select and invoke it correctly.

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 description adds no parameter-level meaning despite 8 parameters and only 50% schema description coverage. Required place and practice are described in the schema, but sort values such as change versus pct, direction, limit, lang, and minValue behavior are not explained in either place.

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 resource and operation: a time series of lawyer supply for a state or county. It is clear enough to distinguish a supply-trend query from demand-oriented or market-profile tools, but it does not explicitly differentiate itself from siblings such as supply_gap or demand_trend.

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 gives no explicit when-to-use guidance, no exclusions, and no alternatives among the sibling tools. The geographic scope is mentioned, but eligibility is not the same as guidance on selecting this tool versus compare_markets, demand_trend, rank_markets, or supply_gap.

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