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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds useful behavioral context by enumerating the returned metrics (median price, appreciation, rental yield, momentum, migration). There is no contradiction with annotations, and no hidden side effects are implied.

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 dense sentences with no filler. The purpose is front-loaded, and the example earns its place by illustrating both valid input and expected output.

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?

Given the strong annotations, full schema parameter coverage, and presence of an output schema, the description provides nearly everything needed to invoke the tool correctly. The only notable gap is explicit guidance on when to use this tool instead of its sibling market tools.

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 schema already documents both parameters fully (100% coverage), including examples and case-insensitivity. The description adds value with a concrete Austin/TX example that shows how city and state combine and what kind of output results, going beyond the schema without duplicating it.

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 names a specific verb and resource: it 'returns [a] full market report for one US city or metro.' The example ('Austin' / 'TX' returning median price, appreciation, rental yield, momentum, and migration) concretely establishes what the tool does and distinguishes it from sibling comparison/listing/search tools.

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 clearly signals that the tool is for a single city or metro query, and it explains why state is required ('city names repeat'). However, it does not explicitly name alternatives or state when to prefer compare_markets, list_markets, or search_markets, so it stops short of full routing guidance.

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