tax_get_payer_nace_info

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

Annotations already declare readOnlyHint=true and destructiveHint=false, confirming a safe read operation. The description adds that it retrieves NACE activity codes, offering useful context on data type, but does not disclose additional behaviors (e.g., rate limits, authentication requirements). The bar is lower due to annotations, and the description adds moderate value.

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 a single, front-loaded sentence that communicates the core purpose efficiently. It includes both English and Georgian text, but every word serves to clarify the tool's function without redundancy.

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?

For a simple lookup tool with one parameter and no output schema, the description states what the tool does and what input is needed. However, it lacks details about the output structure or format of the NACE codes, which would help an agent fully understand the return value. Given the tool's simplicity, it is minimally complete but could be improved.

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% with the single required parameter 'said_code' described as 'Taxpayer identification code'. The description does not add any additional meaning or detail beyond what the schema provides, so the baseline of 3 is appropriate.

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 it retrieves NACE activity codes for a taxpayer, using a specific verb ('Get') and resource ('NACE activity codes'). The tool name and description together distinguish it from sibling tools like tax_get_payer_info, making its purpose unambiguous.

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 implies usage when NACE codes are needed, but it does not explicitly state when to use this tool versus alternatives, nor does it provide context or exclusions. The purpose is clear but usage guidance is minimal.

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