aidoo_get_expiring_contracts

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

There are no annotations, and the description only states the basic purpose. It does not disclose any behavioral traits such as read-only nature, default limits, pagination behavior, or how date boundaries are handled.

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 that is front-loaded and directly states the tool's purpose. It contains no unnecessary information and is easy to parse.

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?

The description is concise and sufficient for a basic query tool, with all parameters documented in the schema. However, it omits details about return format and pagination behavior, and there is no output schema to compensate. The implicit return of a list of contracts is clear from the verb 'finde alle', but a bit more detail would make it complete.

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 input schema provides full descriptions for all four parameters (min_end_date, max_end_date, limit, offset), covering 100% of the parameters. The description adds no additional parameter-specific meaning beyond what the schema already provides.

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 'Finde alle Verträge die in einem bestimmten Zeitraum auslaufen' clearly specifies the action (find) and resource (contracts) with a specific filter (expiration date range). This distinguishes it from sibling tools like list_contracts or get_contract.

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 implies usage for finding expiring contracts in a date range, but it does not explicitly mention when to use this tool over alternatives such as aidoo_list_contracts. No exclusions or preconditions are provided.

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