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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds useful data-scope context ('full awards as contractor and notices as buyer'), but says nothing about auth, rate limits, result volume, or date coverage for a daily-updated dataset.

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 densely packed sentences with the core scope front-loaded and no filler. The telegraphic fragment style is slightly terse but every clause carries 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?

With no output schema, the description partially compensates by naming the return categories (awards vs notices), but omits pagination, date-range behavior, and result limits for what is a daily-updating dataset. Adequate but with clear gaps for a discovery-style tool.

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 100%, so the baseline is 3. The description largely restates the schema ('Identify company by name, KRS, or NIP' and 'Keyed by NIP'), and the schema itself already marks NIP as 'preferred for TED', so it adds no meaning beyond structured fields.

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?

States a specific verb and resource ('Get TED EU-threshold public procurement') with a defined scope that sets it apart from generic procurement retrieval. However, it never distinguishes itself from the near-identical siblings get_company_procurement and get_company_public_tenders, so the agent cannot tell which EU/PL tender tool to pick.

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?

There is no when-to-use guidance and no exclusion relative to the closest siblings (get_company_procurement, get_company_public_tenders). The only routing hint is the identifier preference, which is about parameters, not about tool selection.

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