Fetch full details for a OneHome listing

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

Description adds significant behavioral context beyond annotations: defaults for group_id and include_description, extracted_features processing, lot_size handling (null for condos), raw description omission. Annotations (readOnlyHint, idempotentHint, openWorldHint) are consistent and complemented.

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?

Single dense paragraph that packs a lot of info. Could be more structured (bullets) but every sentence adds value; front-loaded with purpose.

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?

Highly complete: no output schema, but description details return fields comprehensively. Covers all 5 parameters, defaults, edge cases (lot_size null for condos), and behavioral notes. Agent can invoke correctly.

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?

Only 20% schema coverage, but description explains all 5 parameters: url/listing_id as identifier options, group_id session default, include_description default false with rationale, saved_search_id implied. Adds meaning far beyond bare 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?

Description clearly states it fetches full details for a single OneHome listing by id or portal URL, listing many specific fields returned. It is distinguished from siblings like onehome_get_by_address and onehome_search_properties.

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 clear context on when to use (fetch details by id/URL) and defaults (group_id to session, include_description false). Lacks explicit when-not-to-use and alternative sibling references, but the purpose is clear enough.

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