check_jurisdiction_transfer

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

There are no annotations, so the description bears the full burden of behavioral disclosure. It only states the tool checks permission; it does not disclose the return type (e.g., boolean, reason list), whether it is read-only, or how the constraint types interact with the input parameters. This is insufficient for an agent to predict tool behavior.

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, well-front-loaded sentence with no wasted words, containing the core purpose and example constraints. It is appropriately concise for a simple tool, though it sacrifices necessary elaboration for brevity.

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 the absence of an output schema and annotations, the description should explain what the tool returns and how constraints map to the parameters. It does neither, so an agent would not know what to expect from the call or how to interpret the result. The tool is simple, but the description leaves too much unspecified.

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 40% (sourceJurisdiction and targetJurisdiction have descriptions; purpose, transferConstraints, and processingRestrictions are undocumented). The description adds no detail about these undocumented parameters and only references constraint names, which are not explicitly mapped to any parameter. It does not compensate for the 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 states the tool checks whether a data transfer is permitted under jurisdiction constraints, using a clear verb ('Check') and specific resource ('data transfer'). It also lists three constraint types (EU_ONLY, GDPR_ADEQUATE_ONLY, NO_CROSS_BORDER), which helps distinguish it from generic check tools, though it does not explicitly differentiate from the many sibling 'check_*' tools.

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 guidance is provided on when to use this tool versus alternatives. The description implies it is for jurisdiction-related transfer checks, but with siblings like check_purpose_permitted, check_combination_permitted, and check_usage_permitted, the absence of explicit usage context or exclusions leaves the agent without a clear selection basis.

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