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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered; the description adds genuinely new behavioral context about content: seasonally adjusted annual rate, year-ago and pipeline-peak comparisons, the Fed survey quarterly cadence, and 30-day SOFR. It omits freshness/latency and whether the data is cached or live, keeping it below a 5.

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?

One dense but well-ordered sentence: the primary Census series lead, secondary Fed/SOFR sources follow, and the optional parameter closes it. The parenthetical lists carry real information rather than padding, so nothing is wasted.

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?

There is no output schema, so the description must convey what comes back; it does so by enumerating each series and the comparison bases (year-ago, pipeline peak). Only minor gaps remain, such as units/format of the returned values beyond 'annual rate'.

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?

With a single parameter at 100% schema coverage, the schema already defines the 0–60 range and default. The description's 'Optional monthly history' only restates optionality and the quarterly alignment of the Fed series, adding marginal semantics 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?

States a specific verb and resource ('Latest U.S. apartment construction numbers') and enumerates the exact metrics and sources (Census starts/permits/under construction/completions, Fed loan officer survey, SOFR). It does not name or differentiate itself from siblings like compare_construction_options or size_construction_loan, so an agent must infer the split.

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 implies this is the market-context data source, but never says when to call it versus compare_construction_options, get_build_timeline, or size_construction_loan. No exclusions or prerequisites are given; the agent must infer routing from the topic alone.

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