immigration_status_guide

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

No annotations provided, and description only notes 'DEMO' without detailing behavior, side effects, authentication needs, or output structure. Leaves agent uncertain about the tool's operation.

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?

Extremely concise single sentence, but sacrifices necessary detail. Structure is minimal and front-loaded with the core purpose, yet incomplete.

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 two parameters with no schema descriptions and no explanation of output, the description is insufficient. Output schema exists but is not referenced; agent cannot infer how to invoke or interpret results.

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 has 0% description coverage, and description fails to explain how 'status' and 'country' parameters affect the response. No added meaning beyond parameter names.

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?

Description clearly states it answers common immigration questions for Kenyans in USA, UK, or Canada, and includes 'DEMO' to indicate its nature. It distinguishes from sibling tools like diaspora_tax_guide or dual_citizenship_guide, but could be more specific about the scope of questions.

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 on when to use this tool versus alternatives; the demo annotation hints at limited applicability but lacks explicit instructions or exclusions.

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