regdata_krs_fullnames

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

No annotations are provided, so the description must cover behavioral aspects. It explains the tool downloads a public PDF extract and returns names, roles, and metadata. However, it lacks details on error handling, rate limits, or authentication needs, making transparency adequate but not exhaustive.

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 description is three sentences: first states purpose, second explains why it's needed, third provides usage instructions. Every sentence adds value with no redundancy, making it front-loaded and efficient.

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?

Given no output schema, the description mentions return values (names, roles, metadata). For a tool with one parameter and no required fields, the description provides sufficient context for basic use. It could clarify the output format (e.g., JSON array) but is largely complete.

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 only shows maxItems with additionalProperties true. The description adds significant meaning by explaining the freeform input should be a flat object with name, tax ID, or registration number, and references regdata_describe for field details. This compensates for the schema's lack of specific property definitions.

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 clearly states the tool extracts full non-anonymized board member & shareholder names from Polish KRS, contrasting with the censored official API. This specific verb+resource combination distinguishes it from numerous sibling tools like regdata_germany_handelsregister or regdata_spain_company_directory.

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 tells users to pass search input as a flat object and suggests calling regdata_describe first if unsure of fields. This provides clear usage context and an alternative tool for field discovery, though it does not explicitly state when not to use this tool.

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