Check Jurisdiction Transfer

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the jurisdiction-constraint vocabulary but says nothing about the outcome shape (permitted/denied), what the constraint strings mean, or whether a denial is blocking. Modest added value over annotations, hence a 3.

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?

A single front-loaded sentence with no padding. It is efficient, though the parenthetical token list would be more useful tied to the transferConstraints parameter.

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 5-parameter compliance-check tool with no output schema and 40% schema coverage, the description omits the decision semantics an agent most needs: which constraints are honored, how the three required params interact, and what a permitted vs. denied result means. Adequate as a label, insufficient as an invocation guide.

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 only 40%: sourceJurisdiction and targetJurisdiction carry ISO 3166-1 alpha-2 descriptions, but purpose, transferConstraints and processingRestrictions are bare. The description names three constraint tokens that do not even map to a documented enum on transferConstraints, so it neither documents the params nor compensates for the coverage gap.

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+resource: checking whether a data transfer is permitted under jurisdiction constraints, and names the constraint vocabulary (EU_ONLY, GDPR_ADEQUATE_ONLY, NO_CROSS_BORDER). It does not, however, explicitly distinguish itself from the many sibling checks (check_purpose_permitted, check_combination_permitted, check_usage_permitted), so an agent must infer the split.

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, when-not-to-use, or alternative routing is given. The agent is not told whether this belongs in a pre-transfer gate, whether it should be paired with check_purpose_permitted or check_combination_permitted, or what to do when the check fails.

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