Get my saved Redfin searches

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

The description adds value beyond annotations by specifying the data source (HTML page), authentication requirement ('Requires the user to be signed in'), edge case handling (empty array), and reinforcing read-only safety. Annotations already mark it as readOnlyHint, openWorldHint, and idempotentHint, so the description enriches with non-redundant context.

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 concise with four sentences, each adding unique information: what it does, structure of entries, requirement, edge case, and safety. No redundancy or wasted words.

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?

Considering there are no parameters and no output schema, the description covers the tool's purpose, required authentication, edge case, and safety. It could optionally detail the output format more, but the provided structure is sufficient for a simple retrieval tool.

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?

There are no parameters in the input schema, and schema description coverage is 100% (trivial). The description does not need to add parameter details, and it doesn't. Baseline for zero parameters is 4, and the description adequately explains the tool's inputs implicitly.

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 retrieves the signed-in user's saved searches from redfin.com, specifying the data source (saved-searches page HTML) and the structure of each entry (url, region_segment, display_text). This distinguishes it from siblings like redfin_get_saved_homes, which retrieves saved homes.

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 mentions that the user must be signed in and that an empty array is returned if none exist. However, it does not provide explicit guidance on when to use this tool versus alternatives like redfin_get_saved_homes or other search-related tools, leaving the agent to infer from the name.

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