Bulk-fetch homes.com properties (structured records only)

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

Annotations already declare readOnly, openWorld, idempotent. Description adds significant context: results ordered to match input, per-row error handling, status field, omitted description by default, hard deadline with pending status. No contradictions with annotations.

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?

Description is verbose and runs as a single paragraph. While informative, it could be more structured (e.g., bullet points) for easier parsing. Still front-loaded with main purpose, but dense.

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?

Comprehensive coverage of input, behavior, return fields, error handling, deadline, and comparison with alternatives. No output schema exists, so description carries full burden and does so effectively.

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 coverage is 100% so baseline is 3. Description adds context: urls come from search results, include_description default false, and notes that urls can be paths. Provides reasonable added value beyond schema.

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?

Explicitly states 'Fetch up to 200 homes.com properties in one call and return their structured records.' Clearly distinguishes from sibling tools like homes_get_property (single) and homes_compare_properties (limited to 8 with summary).

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?

Provides explicit guidance: 'Use this instead of looping homes_compare_properties when you just want the records.' Also implies when not to use by referencing alternatives. Covers ordering, error handling, and pending behavior.

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