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

Annotations already declare readOnlyHint=true, and the description adds behavioral context: it is a 'transparent intermediate step' that returns filters and bounds carrying 'near <place>' intent. No contradictions. The description enriches the agent's understanding of the tool's non-destructive transformation role.

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 two sentences long, front-loaded with the main purpose, and every sentence earns its place. No redundant or filler content.

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 low complexity (1 parameter, no output schema), the description is complete. It explains the input (raw query), the output (filters and bounds), and how to use the output (forward to search_listings). No gaps.

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?

With 100% schema coverage, the parameter 'prompt' is well-described in the schema itself. The description adds further value by stating the parameter should be 'the user's raw query,' reinforcing its purpose and tying it to the usage instructions.

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 that the tool translates a natural-language property-search sentence into a structured filter payload compatible with search_listings. It uses a specific verb ('Translate') and resource ('natural-language property-search sentence'), and distinguishes itself from siblings by explaining its role as an intermediate step before search_listings.

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 tells when to use the tool ('pass the user's raw query here') and what to do with the returned data ('forward the returned filters... to search_listings'). It provides clear context, though it does not explicitly mention when not to use it or alternatives.

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