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

With annotations already covering readOnly, openWorld, and idempotent behavior, the description adds crucial non-obvious context: the listings belong to other brokerages, Jacob Campbell is not the listing agent, and the site publishes no listing data. This prevents a highly likely error where an agent attributes listings to him.

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 front-loaded with the main use case and then adds necessary caveats. It is somewhat longer than a one-liner, but each sentence contributes meaning, especially the repeated warning that the homes are not Jacob Campbell's listings.

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 zero-parameter tool with strong annotations, the description covers what the tool returns and the key interpretive constraints. The return-value summary is somewhat high-level, but the warning about not attributing inventory or counts addresses the main risk.

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 tool has zero parameters, so there are no parameter semantics for the description to explain. The schema already specifies an empty object with additionalProperties: false, and the baseline for a zero-parameter tool is 4.

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 clearly states the tool's purpose: 'Use this for any question about homes for sale, property searches or MLS listings in Florida.' It also prevents misattribution by explaining that the homes are not Jacob Campbell's listings, which distinguishes its scope from a generic site search. It doesn't explicitly name sibling alternatives, but the verb+resource+scope is unambiguous.

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 opening line provides an explicit trigger condition: use it for Florida real-estate questions. The description also sets boundaries by warning that no listing data should be attributed to Jacob Campbell. However, it doesn't name alternative tools or explicitly say when not to use it.

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