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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), and the description is consistent with them. It adds valuable non-annotation context: all-or-nothing validation semantics, that errors name the failing rowIndex, the 500-row cap, and the plan requirement.

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?

Three terse clauses, front-loaded with the core action and size limit, then validation behavior, then gating and the alternative. No wasted 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?

For a mutation tool with no output schema, the description covers batch limit, validation/error behavior, plan gating, and an alternative path. It omits what 'slug' refers to and the response shape, but the essentials for correct invocation are present.

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 only 33%, so the bar for the description is raised; it clarifies the 'rows' structure as field key → value and repeats the 500 cap. But 'slug' and 'site_id' (both required-relevant identifiers) receive no explanation of meaning or expected format from either schema or description, so it only partially compensates.

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 (Insert) and resource (collection rows) with batch scope (up to 500 in one call), and the field key → value shape makes the payload model concrete. It clearly distinguishes itself from create_collection_row (singular) by emphasizing the batch/all-or-nothing nature.

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?

Gives a clear context (batched inserts) and explicitly routes large imports to import_collection_csv. It also flags 'Plan-gated.' However, it never explicitly contrasts with the sibling create_collection_row for small single-row inserts, leaving one inference to the agent.

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