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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds no behavioral context of its own — nothing about what is returned (a status flag? a tract ID?), coverage of the underlying dataset, or how the point is resolved to a tract.

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?

Single short sentence with zero padding, which is good, but the brevity is under-specification rather than economy — the one clause delegates all substance to another tool.

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?

No output schema exists, so the description should explain what a caller gets back, and it does not. For a geo lookup with two undescribed parameters and no return information, the definition leaves the agent guessing on the majority of what it needs.

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 0% and the description supplies no meaning for lat/lon beyond the obvious names. It does not state coordinate format, expected range, precision requirements, or how boundary-crossing points are handled.

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 'Same as lookup_address for a latitude/longitude point' defines the tool purely by reference to a sibling; the actual function (Opportunity Zone status) appears only in the title, not the description. An agent that has not read lookup_address's definition learns nothing about what is returned or what resource is being looked up.

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 phrase 'for a latitude/longitude point' implicitly routes the agent here when it holds coordinates rather than an address, which is a usable selection signal against lookup_address. However, no explicit when/when-not statement or prerequisite is given.

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