departi_check_tax

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds context about the analysis scope ('Treaties, DN regimes, social security') and the advisory nature, which adds value beyond annotations.

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?

Two sentences efficiently convey purpose, scope, and advisory nature. No extraneous content; every sentence adds value.

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?

The description covers the core purpose but omits details on output format, parameter usage guidance, and edge cases. With 9 parameters and no output schema, the description could be more comprehensive to aid correct invocation.

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 only 33%, with 3 of 9 parameters having descriptions. The tool description does not elaborate on any parameter meanings, leaving a significant gap. The description fails to compensate for low schema coverage.

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 performs 'tax residency analysis' for 43 countries, specifying the resource (tax residency) and action (analysis). It distinguishes from sibling tools like departi_check_visa and departi_track_schengen by focusing on tax and social security.

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 for tax-related queries with 'Tax residency analysis' and 'Advisory only.' While no explicit when-to-use or alternatives are given, sibling tools cover distinct domains (visa, Schengen, transport), providing clear contextual separation.

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