tax_get_comp_act_old

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

Annotations declare readOnlyHint=true and destructiveHint=false, so the tool is clearly a safe read operation. The description adds that the output includes 'DESC + 11 data columns', providing some output structure context beyond annotations. However, it does not elaborate on other behavioral aspects like rate limits or authorization.

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 sentence with a parenthetical translation, which is concise and front-loaded with the core purpose. No unnecessary words, but it could be slightly more structured by separating the output format hint.

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 'DESC + 11 data columns' to hint at output structure. However, it lacks details on potential error conditions, pagination, or usage constraints, making it minimally adequate for a simple read tool.

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?

Input schema covers all 4 parameters with descriptions (100% coverage), so the description does not need to add parameter details. However, the description does not provide any additional semantics beyond what the schema already offers, such as constraints or relationships.

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 'Get comparison act in old format' with additional detail 'DESC + 11 data columns', providing a specific verb and resource. It also includes a Georgian translation, aiding clarity. The sibling 'tax_get_comp_act_new' is distinct, so purpose is well-defined.

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 there is a new format version via the name 'old format', but it does not explicitly state when to use this tool versus alternatives like 'tax_get_comp_act_new'. No usage context or exclusions are provided.

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