meineba_gespeicherte_suchen

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so safety and repeatability are covered. The description adds only the fact that the saved searches carry e-mail alerts, which is a data attribute rather than a behavior; it says nothing about authentication requirements, scope (all saved searches vs. a subset), or ordering.

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?

A single short phrase, front-loaded with the resource and its distinguishing feature. Nothing is wasted, but the terseness is close to under-specification rather than deliberate 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?

With no parameters and no output schema, the description carries the burden of explaining what comes back and under what conditions, and it does not: no indication of the returned fields (search terms, alert frequency, status) or the authenticated meinBA context implied by the sibling login tools.

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 tool takes zero parameters, which is the baseline-4 case. Nothing in the description is needed to disambiguate inputs, and none are introduced that the schema lacks.

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 names the resource (saved job searches / Suchaufträge) and a distinguishing attribute (e-mail alerts), but uses a bare noun phrase with no verb, so it never states whether it lists, retrieves, or manages them. An agent can guess it is a read against the stored-search collection, but it is not confirmed. Siblings like search_jobs and meineba_merkliste are not referenced, so differentiation is left to the name.

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?

There is no when-to-use guidance at all. It does not say whether to call this instead of search_jobs when the user wants their own saved searches, nor any prerequisite such as being logged in via meineba_login_start.

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