get_ai_unanswered

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

With no annotations, the description carries the full burden of explaining behavior. It says the tool returns unanswered questions but does not define what qualifies as 'unanswered,' whether it's read-only, or what the response structure is. The PRO plan note adds minimal context.

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 extremely brief (8 words) and front-loaded with the key term, but it is a fragment rather than a complete sentence. It is concise but lacks grammatical structure, which contributes to ambiguity.

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 tool with no parameters, the description gives a basic sense of the returned data (unanswered questions) but omits details like time range, output fields, or how 'unanswered' is determined. Without an output schema, these details would be valuable.

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 are zero parameters, so there is nothing to explain. The empty schema with additionalProperties true is unusual, but the description does not need to compensate for missing parameter docs. Baseline 4 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 identifies the resource (unanswered AI chat questions) but lacks an explicit verb, reading as a noun phrase rather than a clear action like 'List' or 'Retrieve.' It implicitly distinguishes from get_ai_questions, but not explicitly.

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 is provided on when to use this tool versus siblings like get_ai_questions or get_negative_feedback. The only contextual note is a plan requirement, which is a restriction rather than usage direction.

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