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

With no annotations provided, the description carries the full burden of behavioral disclosure. It usefully discloses the per-call cost and blockchain network, which is important for an agent deciding whether to invoke the tool. However, it does not mention whether the operation is read-only, what inputs trigger the cost, what ranking methodology is used, or any failure conditions.

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?

Two short sentences deliver the core purpose and the most critical operational detail (cost) with no filler. The description is appropriately front-loaded and every sentence earns its place.

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 covers the main purpose and cost, and an output schema exists, so the agent may not need return-value details. However, it omits guidance on choosing between company_url and company_profile, the meaning of the less obvious fields, and how this tool relates to tenderfit_payment_details or tenderfit_pulse. For a paid tool with six parameters, this is adequate but notcomplete.

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 description adds no parameter-level meaning beyond the schema. Schema coverage is 50%, and parameters like days, limit, and corpus_limit are left undocumented in both the schema and the description, so the agent receives no help understanding how to set them or what corpus_limit means.

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 uses a specific verb ('Find and rank') and a clear resource ('live UK public procurement opportunities'), so an agent can tell what the tool does. However, it does not explicitly distinguish itself from its siblings, such as tenderfit_payment_details or tenderfit_pulse, so it misses the strongest form of differentiation.

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 the tool should be used when an agent needs to discover and rank live UK tender opportunities, which is clear context. It does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives like tenderfit_pulse, so the agent must infer routing from tool names.

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