tax_get_tp_info_public

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds that the info is 'public', reinforcing the read-only nature, but does not disclose additional behavioral traits like rate limits or authentication requirements. With annotations present, the bar is lower, and the description adds minimal extra context.

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 of 12 words, front-loaded with the action and resource. Every word is meaningful, with no filler or redundancy. It is efficiently structured for quick parsing.

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 tool with one parameter and no output schema, the description adequately explains what the tool returns and its purpose. It does not detail the return format or pagination, but for a public info lookup, this level of completeness is sufficient. A slightly richer description of the output structure could improve it, but it is not essential.

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%, so the input schema fully describes the single parameter 'tp_code'. The description does not add any additional semantic meaning beyond what the schema already provides. According to the rule for high schema coverage, baseline is 3.

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 verb 'Get', the resource 'public taxpayer info', and specifies the data fields returned (name, legal form, status, VAT, address). It distinguishes itself from sibling tools like 'get_name_from_tin' and 'tax_get_legal_person_info' by emphasizing 'public' info by TIN.

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?

No explicit guidance on when to use this tool versus alternatives. The description implies it's for basic public info, but does not mention exclusions or when not to use it. Sibling tool names provide some implicit differentiation, but the description lacks direct usage advice.

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