redfin_agent

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds context about return format (JSON/CSV) and error conditions (missing API key, rate limit, request failure), which complements annotations without contradiction.

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 well-structured with clear sections, concise sentences, and no redundant information. Every sentence serves a purpose, making it easy for an AI agent to parse quickly.

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 tool's complexity (1 parameter with sub-properties), rich annotations, and presence of an output schema, the description is complete. It covers purpose, usage, parameters, return type, and error cases, leaving no gaps for the AI agent.

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?

Despite 'Schema description coverage: 0%' in context, the actual schema input shows descriptions for each parameter. The description adds value by summarizing the required URL and optional parameters (tld, country_code, output_format) and explaining their purposes, going beyond the schema's individual descriptions.

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 'Retrieve parsed Redfin real-estate agent profile data' and lists the specific data returned (name, contact, brokerage, ratings, transactions). It also explicitly distinguishes from property/search tools in the 'When NOT to use' section, differentiating it from sibling tools like redfin_for_sale and redfin_search.

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 provides explicit 'When to use' (extracting agent profile, lead building) and 'When NOT to use' (property or search data, with reference to other Redfin tools). This gives clear guidance to the AI agent on when to select this tool versus alternatives.

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