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

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), and the description adds genuine context beyond them: the event source it indexes, the newest-first ordering, and the precise definition of the default filter (funded, not cancelled, completions remaining, deadline not passed). It does not state the default lookback size or any pagination/cursor behavior.

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 dense sentence with the scoping and ordering facts front-loaded and no filler. The nested parenthetical of four open-condition criteria is compact but slightly heavy for one pass.

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?

An output schema exists, so return values need not be explained, and annotations cover safety. However, for a list tool with an undocumented limit and lookbackBlocks, the description should mention paging and the default window size; those omissions leave an agent guessing at result volume.

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 description coverage is 0% for three parameters, so the description must carry all parameter meaning and does not. It obliquely defines what includeClosed toggles and hints at lookbackBlocks via 'lookback window', but never names the parameters, states the default lookback, or explains the limit cap of 200.

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 (tenders), its origin (ERC-8414 TaskUpdated events), the scope (lookback window) and ordering (newest first), so an agent can tell this is a browse-style listing distinct from the sibling tender_inspect. It stops short of an explicit verb like "list", relying on the name for that.

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?

Usage is only implied: the default open-only filter makes it read as a 'browse currently actionable tenders' tool, from which an agent can infer tender_inspect should be used for a single item. There is no explicit when-to-use or when-not-to-use statement, and no sibling is named as an alternative.

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