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

Annotations already declare the tool read-only, idempotent, and open-world; the description adds useful context about response fields ('gesamt', 'weitere'), pagination behavior, and the incremental-fetch strategy using 'seit'. This goes beyond what the annotations alone provide.

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 front-loaded with the core purpose and then provides operational details in a logical order. It is somewhat dense and the final sentence about deciding what fits the user is slightly rhetorical, but overall every sentence contributes useful 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?

For a read-only list tool with 7 optional parameters and no output schema, the description covers default behavior, pagination, and incremental syncing sufficiently for an agent to invoke it correctly. It does not describe individual entry fields, but that is a minor gap given the schema coverage and the page/response metadata it does explain.

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 schema already covers all 7 parameters with descriptions, so the baseline is 3. The description adds value by explaining how 'seite' relates to the 'weitere' response field and how 'seit' enables maintaining an up-to-date local copy, which the raw schema does not convey.

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 states a specific verb and resource: 'Liest Eintraege von Open Platform' and clearly identifies the domain as a location-based marketplace for offers and requests. This distinguishes it from sibling tools like chats, messages, or profile management even without naming them explicitly.

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?

The description gives clear operational guidance: all filters are optional, fetching everything is the default, and pagination via 'seite' while 'weitere' is true is explained. It also explains the incremental sync use case with 'seit'. However, it does not explicitly name alternatives or state when not to use this tool.

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