proppulse

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not mention rate limits, data freshness, required permissions, side effects, or any other behavioral traits. It only states coverage is global and includes prices per endpoint, but this is insufficient for an API with 23 parameters and 10 actions.

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 starts with a clear title and purpose, but then lists all 10 endpoints with details, making it somewhat lengthy. While structured with bullet points, it could be more concise by grouping or omitting redundant information. It is adequately front-loaded but slightly verbose.

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 complexity (23 parameters, 10 endpoints, no output schema), the description is incomplete. It does not indicate which parameters are relevant for which action, how to construct requests, or what the response format is. The schema descriptions provide some parameter context, but the tool description lacks necessary operational guidance.

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 the baseline is 3. The tool description does not add any additional meaning to the parameters beyond what is already in the schema; it only lists endpoint names and brief descriptions. The param descriptions in the schema are minimal but present, so the description does not detract but also does not enhance.

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 the tool's purpose as 'Global real estate intelligence API' and lists 10 specific endpoints covering the property lifecycle, distinguishing it from sibling tools that likely cover other domains. However, it does not explicitly state the high-level function of the tool itself beyond being an API.

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 does not provide any guidance on when to use this tool versus alternatives. It lists endpoints but lacks instructions on selecting actions, required parameters for each endpoint, or conditions under which the tool should or should not be used.

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