semantic_search

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 states that it searches saved conversions and works across languages, but it doesn't disclose the return format, ranking behavior, or any limitations such as authentication or rate limits. This is minimal disclosure for a tool with no annotation support.

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 concise sentences, front-loading the main verb and resource ('Search your saved conversions...') and adding a useful cross-language capability in a short second sentence. There is 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?

The tool is simple with two parameters and no output schema, but the description omits any mention of result format or ordering. It covers the core functionality adequately but misses additional context that would help an agent understand expected outcomes, especially since there are no annotations or output schema to fill the gap.

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 input schema fully describes both parameters: query as 'Natural language search query' and limit as 'Max results (default: 5)'. With 100% schema coverage, the description adds no additional parameter semantics, so the baseline 3 applies.

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 searches saved conversions using natural language, which is a specific verb and resource. The cross-language feature adds a distinguishing detail that separates it from sibling conversion tools like convert_url and get_conversion.

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 intended use is implied—searching saved conversions—but there is no explicit guidance on when to prefer this over alternatives like get_conversion, nor any when-not-to-use exclusions. The context from sibling names helps, but the description itself lacks direct usage instructions.

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