batch_add_true_false

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

No annotations are provided, so the description carries full burden. It mentions clear_existing deleting items, but lacks details on error handling, rate limits, authentication needs, or side effects beyond deletion.

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?

Description is concise with two sentences, front-loading purpose and immediately clarifying the question format and clear_existing behavior. No wasteful words.

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?

Has output schema, reducing need for return value explanation. However, with 4 parameters and no annotations, the description should cover 'form_id' and 'start_index' more explicitly. Currently adequate but not rich.

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 must compensate. It explains the 'questions' dict format and 'clear_existing' effect, but does not define 'form_id' or 'start_index', leaving gaps.

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 it's for bulk adding True/False questions ('Bulk add True/False questions'), which differentiates it from sibling tools like add_true_false_question (single question) and raw_batch_update (generic).

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 implies usage when adding multiple True/False questions in one call, but does not explicitly compare to alternatives like add_true_false_question or raw_batch_update, nor specify when NOT to use it.

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