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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false/openWorldHint=false, so the safety profile is covered. The description adds real value beyond that: the coverage window ('period ending 2025+'), the primary key (KRS), and the explicit null-when-undisclosed behavior for a read tool whose empty result could otherwise be ambiguous.

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 plus a short trailing clause; the resource is front-loaded and no sentence is filler. It is information-packed but readable and appropriately sized.

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 carries the return-value burden and does so adequately by naming the fields (creditor, amount, secured debt, asset, KW numbers) and the null case. Minor gap: no guidance on choosing among the three identifier parameters.

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 all three identifier parameters are already documented with format details (10 digits). The description only adds 'Keyed by KRS' and does not resolve precedence among krs/nip/name, so it stays at the baseline.

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 (secured liabilities from financial-statement notes) and enumerates exactly what is returned (mortgages, pledges, transfers, assignments) with the fields attached. This clearly separates it from siblings like get_financials and get_company.

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 implied by the content scope and the note that results are 'keyed by KRS' and 'null when nothing is disclosed', but the description never says when to prefer this tool over get_financials or any alternative, nor are prerequisites or exclusions named.

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