house_pricesv2estimate

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 only states it returns a list of estimates, missing critical details like whether it's a read-only operation, if it requires authentication, rate limits, pagination behavior, or error handling. This is inadequate for a tool with parameters and no output schema.

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 is a single, efficient sentence with no wasted words. However, it's overly brief and under-specified, which impacts its usefulness despite being concise.

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 tool has 3 parameters, no annotations, and no output schema, the description is incomplete. It fails to explain the tool's behavior, return format, or usage context, leaving significant gaps for the agent to understand how to invoke it 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?

The schema description coverage is 100%, so the input schema fully documents the three parameters (geoIdentifier, after, first). The description adds no additional meaning beyond what's in the schema, such as explaining the relationship between parameters or typical values. Baseline 3 is appropriate when 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 'Returned list of estimated house prices' is a tautology that essentially restates the tool name 'house_pricesv2estimate' without specifying the action or resource clearly. It lacks a specific verb and doesn't distinguish from siblings like 'house_pricesv2detail' or 'house_pricesv2get_area'.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites, context, or exclusions, leaving the agent with no direction on usage relative to siblings such as 'house_pricesv2auto_complete' or 'house_pricesestimate_deprecated'.

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