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

As there are no annotations, the description must carry the full load of operational transparency. It fails to disclose critical behavioral aspects such as data latency, data accuracy, or whether the 'serving' state implies a guaranteed operational status for the agent.

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 two-sentence structure is inefficient. The first sentence is an unnecessary, overly detailed internal developer note ('Roadmap probe, not yet served') that is verbose and irrelevant to the agent's task.

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 provides adequate context by naming the data source ('Find a Tender OCDS data') and the target information (supplier contracts). For a simple lookup tool, this meets the minimum viable completeness.

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 coverage is 100% for a single parameter ('supplier'). The description simply repeats this information within the context of the tool's function, providing no semantic value beyond what the structured schema already provides. Baseline score is appropriate.

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 function is to retrieve contract awards for a supplier from specific data sources (Find a Tender OCDS data). However, the opening phrase, 'Roadmap probe, not yet served,' adds informal meta-commentary that slightly detract from the direct functional purpose.

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 offers no guidance on when this tool should be preferred over other lookup tools (e.g., searching company profiles or sanctions lists). It lacks explicit usage constraints or alternatives.

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