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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds the specific data categories returned, which is genuine value, but says nothing about auth requirements, rate limits, caching, or the meaning of 'top' versus other tiers in a lookup with no output schema.

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?

Front-loads what is returned, then the identifier. The inline 'Args:' block is slightly awkward formatting for a description field but wastes no words and the content is dense and relevant.

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?

With no output schema the description wisely lists the returned data categories, and one parameter is fully explained. However, it omits any note on pagination, response shape, or how the 'top' variant differs from the many sibling company/risk tools, leaving a gap an agent may need.

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 description coverage is 0%, so the schema gives only 'string' with no meaning. The description compensates by clarifying that vat_or_taxCode accepts either a VAT number or a tax code for an Italian company, which is exactly the semantic an agent needs to supply the right identifier.

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?

States a specific verb (Returns) and enumerates the exact resource contents: operational credit limits, rating evaluations, risk score history, public ratings, financial positions/profiles for an Italian company. This clearly distinguishes it from generic siblings like get_company_IT_search or get_company_IT_full by being the credit-score/risk tool. It stops short of naming which sibling to prefer when both could fit.

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 when-to-use guidance is given. The 'top' suffix implies a highest-detail tier relative to get_company_IT_advanced/full/search/start, but the description never explains the tier relationship or when an agent should pick this over post_risk_WW_kyc_full or the company lookup tools. The only usage hint is the implicit Italian-company scoping.

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