Create Forms question

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

Annotations declare this is a non-readonly, non-idempotent, open-world write but give no detail. The description adds the crucial fact that the new question always lands at the end, and that the response is the created Question with its id. It does not state auth requirements or failure modes, but the placement behavior is a genuinely non-obvious trait.

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?

Two short paragraphs, front-loaded with the core action and return value, then the body typing and the placement caveat. No filler, though the parenthetical '(note its id)' is slightly terse.

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 2-param write tool with a rich discriminated schema and no output schema, the description covers action, input typing, return value, and the non-obvious append-last behavior with the right follow-up tool. Auth and error handling are the only gaps.

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 100%, so the schema fully documents survey_id and the discriminated body. The description adds framing ('one of 12 typed question schemas discriminated by type') but no syntax the schema lacks. Baseline 3 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?

States a specific verb and resource (append a question to a form) and distinguishes itself from siblings by naming questions_move as the repositioning tool. An agent can tell it apart from forms_questions_update and forms_questions_move without opening any schema.

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?

Clearly implies when to use: when you want to add a question, and explicitly names the follow-up (reposition with questions_move). It does not name update vs create alternatives, but the create-vs-reposition routing is explicit.

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