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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so safety is covered. The description adds real behavioral context beyond them: the response exposes 'gesamt' and 'weitere', pagination terminates when 'weitere' is false, and an incremental-sync pattern via 'seit' is supported. It does not describe rate limits or what fields an individual entry carries.

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?

Front-loaded with the core action and the no-arguments default, then pagination and sync guidance in a logical order. It is somewhat long with all-caps emphasis and visible encoding artifacts ('—'), but nearly every sentence carries usable information.

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 output schema, the description compensates by naming the return keys 'gesamt' and 'weitere' and the loop condition for paging, which is what an agent needs to drive pagination. It still leaves the shape of individual entries undescribed, a minor gap for a 7-parameter listing tool.

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 coverage is 100%, so the baseline is 3; the description earns an extra point by explaining how 'seite' and 'weitere' interact for paging and how 'seit' enables delta sync, which is workflow meaning beyond the per-field schema text. The other filters (art, suche, anzahl, sortierung) are left entirely to the already-complete schema.

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: reads entries from Open Platform, a location-based marketplace for offers (Angebote) and requests (Gesuche). An agent can tell it is a read/list tool over market posts, but the description never distinguishes it from close siblings like meine_treffer or meine_posts, so sibling differentiation is left implicit.

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?

Explicitly says all filters are optional and that calling without arguments returns everything, and it prescribes two concrete workflows: page through while 'weitere' is true, or do an initial full pull then incremental pulls with 'seit'. It also points to kategorien_ansehen for valid 'fachgebiet' values. It stops short of stating when to prefer this over meine_treffer/meine_posts.

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