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

Adds behavioral context beyond annotations: rollover at midnight UTC, same questions for everyone, and the shared nature. No contradiction with readOnlyHint and idempotentHint (both accurate).

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?

Front-loaded with core purpose, but includes a lengthy instruction block. While every sentence is relevant, it could be slightly more concise. Still well-structured and easy to parse.

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 output schema exists, the description covers timing, usage, and behavior thoroughly. It provides all necessary context for an agent to use the tool correctly without needing external details.

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 single language parameter has 100% schema coverage. The description adds value by clarifying that the same five questions are returned regardless of language, and untranslated ones fall back to English. This goes beyond the schema's enum and description.

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 states the tool returns the shared set of 5 citizenship questions with answer keys and explanations. It distinguishes from siblings like get_practice_question or get_mock_test by emphasizing the daily, communal nature and the specific quizmaster role.

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?

Explicitly instructs the agent to act as quizmaster: present one question at a time, never reveal answers before user commits, and give score as N/5. It also suggests directing users to the website for streaks/leaderboard, providing an alternative.

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