ask_question

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does disclose the asynchronous nature of answers, but omits side effects, visibility/persistence of the question, authentication requirements, and how answers will be delivered.

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 two short sentences with the core action and a direct usage pointer. Every phrase earns its place, and the most important behavior is front-loaded.

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?

It is minimally viable: it states the purpose and tells the agent to search first. However, with no output schema, no annotations, and low parameter coverage, it leaves gaps around return values, tag semantics, and what happens after asking.

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 only 25%, and the description does not compensate. It does not explain what title, body, or tags should contain beyond what their names already imply, leaving most parameters under-documented.

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 a specific action and resource: 'Ask the pool a question.' It also distinguishes itself from siblings by noting answers are asynchronous, which separates it from answer_question and search_lessons.

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 instruction to 'Check search_lessons first' explicitly guides the agent to search before asking, which is a clear usage condition. It does not provide full when-not-to-use exclusions, but gives more guidance than most sibling tools.

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