APIbase

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

With no annotations provided, the description carries the full burden. It effectively discloses the specific data fields returned (tax assessment, HOA, photos, etc.) and the data source (RapidAPI/Realtor.com), but omits operational details like safety, idempotency, or rate limits.

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 dense sentences with zero waste: the first front-loads the purpose and enumerates return fields; the second provides workflow guidance and data source attribution. Every clause earns its place.

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 single-parameter lookup tool without an output schema, the description adequately compensates by listing specific return fields and noting the external data source. Could improve by indicating the response structure, but sufficient for tool selection.

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 description coverage is 100%, establishing a baseline of 3. The description reinforces the schema's explanation that the property_id comes from for_sale search results, but does not add significant semantic detail beyond what the schema already provides.

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 opens with a specific verb phrase ('Detailed property information by property ID') and immediately enumerates specific return fields (beds, baths, sqft, etc.), clearly distinguishing this from the sibling 'for_sale' search tool by requiring a property_id parameter.

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?

Explicitly states the prerequisite workflow: 'Use for_sale search first to get property_id', clearly indicating when to use this tool (after obtaining an ID) and implicitly identifying the sibling alternative for the initial search phase.

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