propertieslookup_deprecated

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

No annotations are provided, so the description carries full burden. It mentions the tool is deprecated and suggests an alternative, which is valuable behavioral context. However, it doesn't disclose what 'look for' entails operationally (e.g., read-only vs. mutation, error handling, or data format). For a tool with no annotations, this leaves significant behavioral gaps.

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 concise sentences: one states the purpose, the other gives critical usage guidance. Every word earns its place, and the deprecation warning is front-loaded with an asterisk for emphasis. No wasted text.

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 no annotations and no output schema, the description is minimal but covers key aspects: purpose and deprecation. However, for a lookup tool, it lacks details on return values, error cases, or what 'off-market' means contextually. It's adequate but has clear gaps in completeness.

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%, so the schema fully documents the single 'id' parameter. The description adds no additional parameter semantics beyond implying it's for off-market properties, which is already suggested by the tool name. Baseline 3 is appropriate as the schema does the heavy lifting.

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 states 'Look for off-market property by id' which provides a basic verb+resource combination, but it's vague about what 'look for' means (search, retrieve, check existence?). It distinguishes from the alternative endpoint mentioned, but doesn't clearly differentiate from sibling tools like propertiesdetail or propertiesv3lookup. The purpose is understandable but lacks specificity.

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 explicitly provides when NOT to use this tool: '* Use .../properties/v2/lookup endpoint instead for more data returned.' This gives clear guidance to prefer an alternative for richer data, making it excellent for agent decision-making despite the tool being deprecated.

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