get_directors_history

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

No annotations provided, but description discloses important behavioral traits: returns only current director at S3 with data incompleteness warning, and full history only at S5. Details about parameter non-usage at S3 add transparency. Doesn't mention auth or rate limits, but given no annotations, this is good.

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?

Three sentences with front-loaded purpose. No wasted words; each sentence provides distinct, necessary information (purpose, stage behavior, parameter notes).

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 3 parameters and existing output schema, the description covers stage-dependent behavior and parameter constraints. It doesn't detail output schema, but that's covered by the output schema itself. Sufficient for the complexity.

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 the description adds value by noting that depth_years and include_founders are not effective at S3. This clarifies parameter behavior beyond the 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?

Clearly states 'История смены руководителей и учредителей по ИНН' (History of changes of directors and founders by TIN), specifying the verb (get history) and resource (by TIN). This distinguishes it from sibling tools like check_inn or get_legal_status.

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?

Provides stage-specific behavior: at S3 returns only current director with a warning, full history at S5. Also explains that depth_years and include_founders are not used at S3. While it doesn't explicitly list when not to use or compare to siblings, it gives clear usage context.

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