get_test_infoKey facts about the Canadian citizenship test and oath: format, pass mark, who must take it, how scheduling works, and what happens at the ceremony. Verified against official IRCC sources.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| oath | Yes | ||
| test | Yes | ||
| practice | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and idempotentHint=true, so no additional safety disclosure needed. The description adds that content is verified against official IRCC sources, which implies reliability but does not add behavioral traits 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: first front-loads the key topics, second adds credibility. No wasted words, appropriate length for an info tool.
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?
Tool has output schema, so return structure is covered. Description lists included topics sufficiently. Could hint at whether output is a summary or detailed, but given simplicity, it is mostly complete.
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?
No parameters exist; schema coverage is 100% (empty). The description compensates by detailing the topics covered (format, pass mark, etc.), providing meaningful context for what the tool returns.
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 the tool returns key facts about the Canadian citizenship test and oath, listing specific topics like format, pass mark, scheduling, and ceremony. It distinguishes itself from siblings (e.g., get_mock_test, get_oath_guide) by focusing on general facts rather than specific practice or guidance.
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 explicit when-to-use or when-not-to-use guidance. The description implies it is for general factual reference, but does not direct the agent away from using more specific sibling tools like get_mock_test or get_oath_guide when 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 has a clearly distinct purpose: presence calculation, question lookup/grading, stats, daily challenge, journey stats, mock test, oath guide, practice question, study guide, test day guide, and test info. Even the three question-providing tools (get_daily_challenge, get_mock_test, get_practice_question) are well-differentiated by format and intent.
All tool names follow a consistent verb_noun pattern in snake_case, with most starting with 'get_' (e.g., get_daily_challenge, get_mock_test) and two exceptions (calculate_presence, check_answer) that still adhere to the same verb_noun structure. No mixed conventions.
11 tools is well-scoped for the Canadian citizenship test domain. It covers eligibility calculation, multiple question formats, statistics, guides, and test-day information without being overwhelming or sparse.
The tool surface covers the entire lifecycle: eligibility check (calculate_presence), study resources (practice questions, mock tests, study guide, daily challenge), reference info (test info, oath guide, test day guide), statistics, and a question-answer lookup tool. No obvious gaps for the stated purpose.