create_question

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

Without annotations, the description must disclose behavior. It explains parameters but does not mention side effects (e.g., whether creation is idempotent), what the return value is, or any permissions needed. The focus is on parameter format, not operational behavior.

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 moderately sized with clear bullet-like lines for each parameter. Every sentence adds value, though it could be slightly more compact. The structure is easy to parse.

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 complexity (JSON parameters, multiple types), the description covers parameter formats well. However, it lacks details on return values (output schema exists but not described), constraints on question text, or error handling. Some gaps remain.

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 0%, so the description is the sole source for parameter meanings. It explains each parameter clearly, including formats for options (JSON list with objects) and possibilities (JSON list of strings), and lists values for question_type. This adds significant value beyond the bare schema.

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 'Create a reusable LMS Question,' specifying the verb 'create' and the resource. It distinguishes from sibling tools like create_quiz (creates a quiz) and add_question_to_quiz (adds existing question to quiz), making the tool's role clear.

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 (e.g., add_question_to_quiz) or what steps to follow after creation. No mention of prerequisites or context.

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