bewerte_angebote

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

The description reveals that the tool compares offers to a profile and sorts results, but it does not disclose side effects, required permissions, or error behavior. With no annotations provided, this limited behavioral disclosure is insufficient for an agent to anticipate consequences.

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, front-loaded sentence with no filler words. It efficiently communicates the core action and result.

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 two parameters and no annotations, this description is too sparse to fully prepare an agent. It omits details about input formats, the sorting criterion, and how results are structured, making it inadequate for confident 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?

The description loosely maps to the parameters by mentioning 'Angebote' and 'Profil', but does not explain their types, formats, or relationships beyond the schema. With 0% schema description coverage, the description should offer more detail, such as what angebote entries look like or what profil_pfad points to.

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 evaluates offers against the profile and returns sorted matches, using a specific verb and resource. It differentiates from sibling search/analysis tools by its focus on matching and sorting.

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 about when to use this tool versus alternatives, such as portal_suche or analysiere_echtes_portal. The description lacks any context like prerequisites or exclusions.

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