get_entrepreneur

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

No annotations are provided, so the description must cover behavioral traits. It describes the returned data categories but does not mention side effects, permissions, or operational constraints (e.g., whether it is read-only, has rate limits, or requires authentication). The tool name implies read-only behavior, which partially compensates.

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, front-loaded with the purpose and ending with a list of returned data. No extraneous information. Every sentence earns its place.

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?

The description lists high-level return categories (USRIP data, licenses, taxes, risk factors, affiliated persons) but lacks details on the structure or format of the response. Since there is no output schema, this is a gap. For a tool with 4 optional parameters, the description is adequate but not comprehensive.

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% (all parameters have descriptions). The description adds no additional meaning beyond the schema; it simply lists identifier types in the first sentence. The source parameter is described in the schema, and no new constraints or relationships are provided.

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's purpose: retrieve information about an individual entrepreneur from ЕГРИП by OGRNIP, INN, or OKPO. It lists the types of data returned (USRIP data, licenses, taxes, risk factors, affiliated persons). This distinguishes it from sibling tools like get_company (legal entities) and get_person (individuals), which cover different entities.

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 provides clear context that the tool is for individual entrepreneurs, enabling an agent to infer when to use it over alternatives (e.g., use get_company for legal entities). However, it does not explicitly state when not to use it or specify prerequisites.

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