get_ai_questions

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

The description discloses a plan requirement (PRO plan or higher), which is a minimal behavioral trait. However, with no annotations, it fails to disclose read-only status, return format, pagination, or potential errors, leaving the agent without critical behavioral 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 concise with no wasted words, and the core information appears first. However, its brevity borders on under-specification, but that is addressed in other dimensions.

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 no output schema and no annotations, the description should clearly describe what the tool returns. 'All AI chat questions' implies a list, but there is no mention of response structure, pagination, or whether it is read-only. This is a notable gap for a simple GET 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?

The tool has zero parameters, and the schema is empty. Per guidelines, 0 parameters merit a baseline of 4. The description does not need to explain parameters, and it doesn't, so the schema is sufficient.

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 'All AI chat questions' is a noun phrase with no explicit verb, essentially restating the tool name. It does not specify the action (e.g., 'retrieves', 'lists') or distinguish from sibling tools like get_ai_usage or get_ai_unanswered.

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 or how it differs from alternatives. The only additional statement, 'PRO plan or higher,' is a prerequisite, not a usage guideline.

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