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

The description discloses several behaviors beyond the sparse annotations: update replaces content entirely, blockType is immutable, changes affect only the bank's DRAFT until published, the response hasChanges signals unpublished state, and public template ids are rejected. These are meaningful operational traits not visible in the openWorldHint, idempotentHint, or destructiveHint annotations.

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 dense and front-loaded, and nearly every clause carries operational meaning. However, the long single-paragraph format with multiple embedded asides is somewhat harder to scan; the information density is excellent, but the structure could be cleaner.

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 nuanced tool with no output schema, it covers the essential lifecycle: reading the reference document, add/update behavior, immutable blockType, draft/publish/discard flow, hasChanges in the response, and public-template rejection. Nothing an agent needs to call this tool correctly is missing.

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?

Although the schema already documents all parameters, the description adds practical value: columns must be an object of lists, IDs are opaque handles tied to specific values, array position defines order, and update requires sending all fields even when unchanged. This goes well beyond the schema's baseline documentation.

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 opens with a specific verb and resource: 'Adds or replaces ONE question/item of a question bank', and immediately distinguishes itself from question_bank_delete. The add/update action semantics are fully explained, so an agent can select this tool for item creation and editing without confusing it with siblings.

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?

It gives explicit when-to-use guidance: read the block-type reference before adding to an unpopulated bank, send unchanged fields on update, and use delete/add instead of trying to change blockType. It also routes related actions to question_bank_manage for publishing and question_bank_discard_changes for discarding, and warns that public template ids are rejected.

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