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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds substantive context beyond that: annual contract values in PLN, coverage back to 2008, types of care, regional branches, and largest contracts. It omits auth/rate-limit details, but with annotations covering safety this is a solid disclosure.

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 content is front-loaded and every clause carries information about scope or return shape. The first sentence is dense but not padded; the trailing identifier sentence is short and functional.

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 must carry the return-shape burden, and it does: annual values, year span, care types, regional branch, and largest contracts. Combined with 100% parameter coverage and rich annotations, an agent has enough to call it correctly; only edge-case behavior (provider without NFZ contracts, name collisions) is unaddressed.

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 coverage is 100% and each parameter is documented in the schema, so baseline is 3. The description adds one useful signal — that NIP is the natural key for NFZ data — but does not clarify name-matching behavior or precedence when multiple identifiers are supplied.

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+resource: contracts between a healthcare provider and Poland's National Health Fund, keyed by NIP. This is unambiguous against siblings like get_company_procurement or get_company_public_contracts, which cover different data sources.

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?

Gives clear context for when the tool applies (NFZ/healthcare provider contracts) and how to identify the company by name, KRS, or NIP. It does not, however, state exclusions or prerequisites, e.g., that the company must be a healthcare provider with NFZ contracts, so a negative case would return empty.

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