create_question

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

With no annotations, the description fails to disclose behavioral traits beyond the generic verb 'Add.' It does not mention whether the operation is idempotent, requires authentication, or has side effects, leaving the agent without crucial safety information.

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 a single sentence, which is concise, but the brevity sacrifices essential detail. It is front-loaded with the verb, but the lack of structure or further explanation reduces effectiveness.

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 lack of annotations, no output schema, and an open input schema, the description is severely incomplete. It does not specify expected inputs, return values, or behavior, making it inadequate for the agent to use confidently.

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 input schema has 0 defined properties but allows additional properties (additionalProperties: true). The description adds no meaning about what fields are expected, despite the baseline for zero parameters being 4; the open schema shifts the burden to the description, which is unmet.

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 verb 'Add' and the resource 'new question to the questionary,' making the tool's purpose apparent. However, it does not explicitly differentiate from sibling tools like 'create_question_option,' which adds options to a question, not a question itself.

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 description provides no guidance on when to use this tool versus alternatives, such as update_question or delete_question. There are no prerequisites, exclusions, or context for appropriate usage.

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