Polemia

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

Annotations only cover the generic write/open-world/idempotency profile; the description adds operational facts an agent cannot get elsewhere: 10-60 second latency, the exact return set, and the critical caveat that host_url is single-use and makes that browser the host. It also discloses the content-refusal policy and the facts-vs-opinions scoring model, which changes how the agent should present results.

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 the core action, then constraints, then return values and the mandatory 'Always give the user both host_url and join_url' instruction. It is dense and every sentence carries information, though the return-value sentence is a long run-on that could be split.

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?

Even though an output schema exists, the description supplies the parts an agent needs for correct handling: which URL goes to whom, that host_url works once, and the instruction sentence to forward. Combined with the latency and refusal notes, nothing material is left unstated for a 5-parameter generative tool.

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 description coverage is 100%, so the baseline is 3. The description echoes the 'facts'/'opinions' distinction already documented in the kind parameter's schema description ('scored by what the majority picks' vs 'the most popular answer scores') and adds no detail on language, questions, or for_children_under.

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?

Starts with a specific verb and resource ('Make a new live multiple-choice quiz on Polemia') plus concrete output artifacts (join code, live play on phones), so there is no ambiguity about what the tool produces. It is clearly distinct in spirit from a search tool like find_quizzes, but it never names or contrasts with its siblings, so it falls short of a 5.

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?

Gives explicit positive triggers ('when the user wants a quiz, trivia game or icebreaker for a class, party, family, team or pub quiz') and explicit exclusions ('Topics that target people, politics, war or adult material are refused'). An agent knows both when to call it and when a call will be rejected.

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

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

Annotations already cover read-only, idempotent, non-destructive behavior, and the description adds useful context: one question per day, anonymous answers, free access, and that the answer_url is where voting and results happen. It does not detail potential rate limits or authentication, but those likely do not apply.

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 front-loaded with the purpose, then usage guidance, then return behavior. Every sentence adds relevant information without waste, including the concise 'Free.' note.

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 simple read-only tool with full parameter schema coverage, rich annotations, and an output schema, the description is complete enough. It covers what the tool does, when to use it, and what the response includes, so an agent can call it correctly.

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?

There is only one optional parameter, language, and schema description coverage is 100%; the schema already explains the BCP-47 language behavior. The description does not add any parameter-specific meaning beyond the schema, so the baseline of 3 applies.

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 names the specific resource ('Today's Polemia question') and what it provides: a daily opinion question answered anonymously. It does not explicitly distinguish itself from siblings like find_quizzes, so it falls short of a 5.

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?

It gives explicit usage contexts: when the user wants a question of the day, a conversation starter, or to see what the world thinks. It does not state when not to use the tool or name alternatives, so it is clear but not complete.

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

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

Annotations already declare the safety profile: read-only, non-destructive, idempotent, and closed-world. The description adds useful behavior beyond them, including free/instant access, a result cap of 10, and the returned fields including play_url.

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-loads the core action and resource, then adds the usage condition and return shape efficiently. Every sentence contributes useful selection or invocation context with no wasteful repetition.

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?

With rich annotations, an output schema, and full parameter descriptions, the definition is complete enough for correct selection and invocation. It still adds value by clarifying scope, result count, and the play_url field.

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 description coverage is 100%, so the query and language parameters are already well documented. The description adds no parameter-specific syntax or format guidance beyond what the schema provides, making the baseline 3 appropriate.

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 and resource: searching a public library of ready-made quizzes. It also differentiates from the sibling create_quiz by saying the user 'does not need a new one written,' so an agent can distinguish this retrieval tool from creation.

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?

Gives a clear usage condition: use when the user wants a quiz on a common topic and does not need a new one written. It implies the create_quiz alternative but does not explicitly name it or address the daily_question sibling.

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