regdata_krs_fullnames

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

Describes that the tool downloads public PDF extracts and extracts names, roles, and company metadata. No annotations to contradict. Discloses it performs file retrieval/parsing beyond a simple API call, but lacks details on rate limits or auth requirements.

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 sentences: first states purpose, second explains why this tool is needed (official API censors). Efficient and front-loaded with key info. Could be slightly more structured but overall well-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?

No output schema, but description covers return contents: 'complete names, roles, and company metadata'. Mentions advanced fields beyond schema. Adequately complete for a tool with 3 params and no nested objects.

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%, but description adds meaning: 'Each number will be padded to 10 digits automatically' for krsNumbers, and explains 'aktualny' vs 'pelny' extract types. Adds value beyond schema descriptions.

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?

Specific verb+resource: 'Extract full non-anonymized board member & shareholder names from Polish KRS'. Distinguishes from siblings like regdata_poland_krs_financial by focusing on board/shareholder data vs financial data, and notes it bypasses official API censorship.

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?

Clear context: use when you need complete names censored by official API. Mentions advanced fields via regdata_describe. No explicit when-not or alternatives for other Polish tools, but sibling differentiation is implied.

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