Per-destination pet border-entry requirements — NO account needed. What documents a dog needs to enter a country and re-enter the US. Use this to answer 'what does my pet need to travel to X?' for anyone. Omit destination to list every corridor.
| Name | Required | Description | Default |
|---|---|---|---|
| destination | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description bears full responsibility. It discloses that no account is needed (public access) and that the tool returns border-entry requirements. It does not mention any destructive behavior or rate limits, which is acceptable for a read-only query. However, it could be more explicit about the return format.
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 extremely concise with three short sentences, each providing essential information. No redundant words.
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 tool's simplicity (one optional parameter, no output schema), the description adequately covers the primary use case, who can use it, and how to vary the query. It could be slightly more complete by noting that it returns a plain text list, but overall it is well-rounded.
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?
The description adds meaning to the single parameter `destination` by explaining that omitting it lists all corridors, and that the tool is per-destination. This goes beyond the schema which only lists enum values. The description coverage is 0% by strict measure, but the text does address the parameter.
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 explains the tool's function: retrieving per-destination pet border-entry requirements. It specifies the use case (what documents a dog needs to enter a country and re-enter the US) and distinguishes from siblings by noting that no account is needed and by offering a specific action (omitting destination to list all corridors).
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 explicitly states when to use the tool ('to answer what does my pet need to travel to X?') and provides an alternative usage pattern ('omit destination to list every corridor'). It implies non-use for account-requiring operations but does not explicitly contrast with sibling tools like customs_check_trip_readiness, so a 4 is appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct aspect of pet travel: rules checking, readiness validation, document listing, pet listing, dashboard overview, session prep, signup, and upcoming trips. No overlap in purpose.
All tools start with 'customs_' prefix and follow a verb_noun pattern (e.g., check_rules, list_pets, start_signup), providing a predictable and clear naming convention.
8 tools cover the core workflows for pet border requirements and document management without being excessive. The scope feels well-calibrated for the domain.
The set covers key operations: rule checking, readiness, document listing, and signup. Minor gaps exist, such as no tool for adding or updating pets or documents after account creation, but core informational queries are fully covered.