auto_complete_deprecated

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

No annotations are provided, so the description carries the full burden. It mentions 'Get auto complete suggestion', implying a read-only operation, but doesn't disclose behavioral traits such as rate limits, authentication needs, error handling, or response format. This leaves significant gaps for a tool with parameters.

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 sentence that directly states the tool's function, making it front-loaded and efficient. However, it could be more structured by including key details like resource type, but it avoids unnecessary verbosity.

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 (2 parameters, no output schema, no annotations), the description is incomplete. It doesn't explain what the suggestions are for, how results are returned, or differentiate from siblings, making it inadequate for effective tool selection and invocation.

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 already documents both parameters ('search_term' and 'search_type') with descriptions. The description adds no additional meaning beyond what the schema provides, such as clarifying the purpose of 'search_type' or examples of suggestions. Baseline 3 is appropriate as the schema handles parameter documentation.

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 the tool 'Get auto complete suggestion by term or phrase', which clarifies it retrieves suggestions based on input. However, it's vague about what is being suggested (e.g., properties, listings, addresses) and doesn't distinguish it from sibling tools like 'house_pricesv2auto_complete' or 'v2auto_complete', missing specific resource details.

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. With siblings like 'house_pricesv2auto_complete' and 'v2auto_complete', the description lacks any context, exclusions, or named alternatives, leaving the agent without usage direction.

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