advanced_search

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 does not disclose read-only vs. mutating behavior (though search implies a read), return format, pagination, result caps, or any permissions. The mention of 'UID Webservice' is a marginal backend hint but adds little operational value.

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?

Two concise sentences; the purpose is front-loaded before the filter enumeration. No wasted words, though the second sentence is largely a restatement of schema 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?

Six parameters, a nested personName object, and zero annotations for a search tool that competes with a sibling. The description omits how this differs from search_companies, what results look like, and any combination/AND semantics of the filters. Given the complexity and annotation gap, it is under-specified.

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 every parameter with patterns, defaults, and constraints. The description restates three filter categories (person names, legal forms, canton) without adding syntax, format, or interaction details beyond the schema. 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?

States a specific verb and resource: 'Advanced company search.' It distinguishes itself from the sibling search_companies by the 'advanced' qualifier and hints at filter richness. It doesn't explicitly say how it differs from search_companies, but the purpose is unambiguous.

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 when-to-use, when-not-to-use, or alternative routing is given. There is a sibling search_companies that likely overlaps, yet the description offers no guidance on when to pick this tool over that one. Usage is only implied by the word 'advanced.'

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