portal_suche

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

With no annotations, the description carries the transparency burden. It discloses two behavioral traits: headless operation and conditional login use. This is useful, but it omits other behavioral context like result handling, external effects, or authentication prerequisites beyond the login condition.

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, front-loaded with the core purpose and free of redundancy. It loses one point because essential parameter and usage details are omitted, which is not purely a matter of brevity.

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?

For a tool with five parameters, no annotations, and an output schema, the description is incomplete. It does not explain the required portal_id, optional filters, engine/profil_pfad defaults, or how login integration works, leaving the agent without enough context for reliable 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 0%, and the description does not explain any of the five parameters (ort, query, engine, portal_id, profil_pfad). The description must compensate for missing schema documentation, but it provides no parameter semantics whatsoever.

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's purpose: 'Sucht headless nach Stellen' (searches headlessly for jobs), which identifies the function and resource. However, it does not distinguish this tool from sibling tools like portal_recherche or mehrportal_suche.

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 given about when to use this tool compared to alternatives. The only usage-related comment, 'Login wird nur bei Portalpflicht verwendet', explains login behavior but does not help an agent choose between portal_suche and sibling search tools.

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