set_textbox_style_bulk

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

Discloses key behaviors: same kwarg surface, skipped names, return format with union of changed sub-paths. Lacks mention of atomicity or partial failure handling, but overall transparent for a bulk operation.

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 sentences, front-loaded with purpose, no redundancy. Efficiently conveys key points.

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?

Given 20 parameters and no output schema, the description is adequate but not exhaustive. It explains return value and skipped behavior but does not detail parameter effects or default behaviors (e.g., null meaning). References set_textbox_style for surface, which is helpful if that tool is well-documented.

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 has 20 parameters with 0% description coverage. Description merely references set_textbox_style's kwarg surface without listing or explaining any parameters. Agent would need external knowledge of that sibling tool's parameter semantics.

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 tool applies the same style to multiple textboxes, distinguishing it from the single-textbox sibling set_textbox_style. It also mentions the return structure and pairing with find_textboxes_by_style.

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?

Explicitly says when to use (bulk apply) vs single-textbox alternative, and describes behavior for missing names (skipped, not error). Also suggests pairing with find_textboxes_by_style for discovery.

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