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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. With no output schema, the description's listing of returned fields (titles, short answers, slugs, links) usefully discloses the response shape, but it adds nothing about scoping, ordering, or result size.

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?

Two compact sentences with the collection identity front-loaded and the payload described at the end. The parenthetical city-guide detail is dense but earns its place by explaining what the guides cover.

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 parameterless, read-only, open-world=false listing with no output schema, the description covers what the catalogue contains and what fields come back. The only real gap is the absence of routing guidance relative to its four siblings.

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 takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool is 4. No misleading parameter language is present.

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 the resource precisely — a catalogue of Texas Treasure Map guides (how estate sales work in Texas, plus per-DFW-city guides) — so an agent knows what content comes back. It does not, however, name the verb or distinguish itself from the sibling get_estate_sale_guide, leaving the singular-vs-collection split to inference from names.

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?

There is no when-to-use guidance and no mention of alternatives; the description never says to call this tool to discover available guides before fetching one with get_estate_sale_guide. Usage is only implied by the tool name itself.

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