mt_set_bulk_transform

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'sets' implies a write/mutation operation, it doesn't specify whether this requires special permissions, whether changes are reversible, what happens on partial failures, or any rate limits. The bulk nature suggests potential performance implications that aren't addressed.

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 a single, efficient Japanese sentence that directly states the tool's purpose without any unnecessary words. It's perfectly front-loaded and every word earns its place.

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 ('sets') with no annotations and no output schema, the description is insufficient. It doesn't explain what 'transformed HTML' means, what format the transforms array should contain, what happens after setting, or any error conditions. The bulk operation aspect adds complexity that isn't addressed.

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?

The schema has 100% description coverage, with the single parameter 'transforms' documented as 'array of transformation results'. The description adds no additional parameter context beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 the action ('sets transformed HTML in bulk') and the target ('multiple items'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from its sibling 'mt_set_transform' (which appears to be a single-item version), missing full sibling distinction.

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 like 'mt_set_transform' (presumably for single items) or other content modification tools. There's no mention of prerequisites, timing considerations, or exclusion criteria.

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